I looked at the 2 screenshots and it took me like a minute to see the send button on the new screen.
I am probably very used to the "old" design. If a user will use this product once or twice, yes then the big button at the bottom will be advantaged. But you are biasing the design for new users.
Existing users know exactly where the button is and will now have wasted space because of a gigantic send button.
And the unreasonable hostility towards macOS will have zero affect because in the end the best product wins.
Did the rise of Windows cause long term harm to past generation of engineers? I doubt it since now Windows, which had a gigantic market share, still was forced to implement Linux "compatibility" for developers.
There are three popular operating systems for the modern developer and it's not unreasonable to ask for a build for all of them when presenting a project to a developer focused community.
The rise of a MacOS sort of monoculture certainly affected those developers that were still on Windows. It drove me off of Windows, a system that I otherwise appreciated just fine. I never cared much for MacOS, though, so I went to Linux, but there I'm also constantly feeling the pain of so many developers being on MacOS, as there's so many incompatibilities between the two. So, in the end I guess I prefer things that run everywhere, which this Parrot thing may be in reach of, it being Electron? In that sense I guess I support the ask for a MacOS version. But boy, could the MacOS crowd just stop throwing their weight around?
Edit:
Examples:
* Tools that are only available on MacOS (remember the days when tools were only available on Windows)
* I write a BASH script which then doesn't work for the MacOS coworkers
* Tools that are supposedly platform- independent have Linux-specific errors that get no love because their developers don't care about Linux
I think it's a little much to expect most small outfits to user test on every single Linux distro though. There are tons of programs that may run fine on something like stock Ubuntu, but bring it to another flavor and all of a sudden nothing works.
I have more than 5 years experience with Home Assistant and Zigbee devices.
(No zwave experience)
Generally I am happy with Zigbee, it's super annoying to pair, but for battery powered devices it's unbeatable.
I went from a some AliExpress USB Stick to a ConBee2 to the Home Assistant Yellow.
I use Ikea, Sonoff, Xiaomi (Aqara) Zigbee devices all of them "just work".
The one big thing Zigbee is good at is not requiring you to need some proprietary App, all devices are just paired locally, you don't need to question if that app you just installed phones home.
For general hardware advice:
Overall the Home Assistant Yellow was the best choice overall, I would anyone who doesn't want to spend a ton of time on HA hosting to just buy it.
Everything works pretty flawlessly with it.
Conbee 2 ist still my current stick because I am experimenting with the Matter/Thread Support on the Home Assistant Yellow, sadly without success though.
My best recommendation if you want to tinker with smart devices is get anything that you can flash Tasmota on. (List of Devices https://templates.blakadder.com/ )
Tasmota is an amazing piece of software that runs on your smart device for example a power plug.
My thoughts just from reading the landing page, not having tested it.
I think trying to replace all these Apps
> serves as an all-in-one replacement of Linear, Jira, Slack, and Notion.
is not a wise move. I can see Linear and Jira and maybe Notion, but fighting with Slack just is an uphill battle. There are so many Chat platforms out there and many open source too.
Why would yours be the one to be at least on par with the likes of Slack? Which hasn't really happend for the others either.
JetBrains tried this with JetBrains Space [1] it used to be a knowledge platform and chat platform all with a code hosting platform, CI platform and a little more. But even an experienced dev company like JetBrains gave that up and focused on the core.
I think they should remove the chat part and stick to being a Jira + Notion replacement.
I don't think we should discount a competing product's existence just because it's a David and Goliath situation. If we all had your mindset we'd still be using MSN Chat on Windows XP or something.
Before JIRA became ubiquitous, before Slack even existed, I used to set up company's tools with MediaWiki, Jenkins, IRC, Redmine and GitWeb. The reason I'd choose these is because I knew more or less how to install them. It wasn't based on any sort of comparison of features etc.
Looking back at those days, I'd still take IRC over Slack any time. Just for the self-hosting part, but also because of better integration, simpler interface, simpler way of extending it to fit company's needs.
I'd also take GitWeb over Gitlab, Bitbucket or Gitea. None of the extras offered by these tools add any real value. The only reason I want any Web interface to Git at all is to be able to link to the code from Wiki / chat.
But, Jenkins turned out to be a really bad pick. And so is Redmine. I've tried many popular CI tools, and they are all bad, so, who knows maybe this project will do it better?.. but they don't seem to tell much about how they see things working. I also haven't found a good bug-tracking tool yet. So, maybe this project will make something better? -- Let's hope.
----
Ideally, I'd prefer it if tools around project management standardized around some basic interfaces, so that no single company was tempted to create "package deals" where you choose to use crappy tools because they are packaged together with what you really want. But, I don't think it's clear to anyone what such interfaces might look like. So, this isn't happening probably in this decade... at least.
Thing is: You don't have to be on par with Slack. If that chat is "usable enough" but integrates well with the rest of the system, this can be a swelling point: Directly reference the tickets in a discussion, reassign, update, ... in a native integration.
With such an "Enterprise" system the choice of the chat tool is a lot more a too down decision, than a chat in a social group.
And it isn't like slack is perfect in all regards either ...
The concern wouldn't be if huly chat integrates well with the rest of huly project management, video calls, docs. It would be all the other services your company uses like pagerduty, salesforce, HR apps, etc where Slack has become the "hub" for everything to integrate with.
I think the only way they can capture some part of the market is by doing something the others are not. We don’t need another Jira + Notion clone I think.
I really like Goldshaw Farm[1]. He does yearly breakdowns how is farm performed and the reality is he could not live at all if that was his only income stream.
And I think his scale is most realistic what a developer could achieve when he quit and just wanted to try to farm.
Goldshaw is very informative, but I think he is a bit more of a hobby farmer than a real homesteader. If you have a sophisticated system (and are willing to work hard), you can bring in substantial amounts of money on small acreage.
You should not conclude from that, that it is healthy for every person to do so.