I know it's not a apples to apples comparison, but the same parent company nonetheless. Not a good look after closing the deal on 69 billion for activision blizzard. Couldn't have set aside one of those billions to keep people employed a while longer MSFT?
The parent company wants to know the viability of each business unit independently, one subsidizing another would obfuscate what's working and what isn't.
And secondively, teams/orgs get bloated and keeping them larger than they should be hinders their progress.
I see these changes as net positive in the long run. Especially since it sounds like performance is getting a boost as well. The $props rune isn't something I realized I needed, but it definitely clears up code clarity. The $effect runes makes people think we are going down the React useEffect route... but I didn't see a dependency array attached there waiting to obliterate performance? I'm all for removing a tiny piece of Svelte magic to improve code clarity and performance gains. Seems like a big win to me. Thanks Rich and team!
> The $effect runes makes people think we are going down the React useEffect route... but I didn't see a dependency array attached there waiting to obliterate performance?
This is exactly what SolidJS already does, and SolidJS is #1 in almost all performance benchmarks.
I don't see how it can hurt adoption? Svelte/Sveltekit are already stable. This is simply an update from the Svelte team about how performance is getting even better. If anything, this inspires confidence from me about how the team is constantly looking to improve the product. Svelte 3 to Svelte 4 was pretty much a painless transition too.
A lot of panic in here about how people think this is a Angular v1 to v2 transition all over again. Svelte version updates are largely behind the scenes so there's really not much to upgrade if your app is already built in Sveltekit.
People who haven't tried Svelte/Sveltekit yet are seriously missing out. It's a breath of fresh air in today's UI landscape. The constant performance gains are the cherry on top.
Svelte doesn't exist in a vacuum, and developers have been burned by major version bumps over and over again (Angular, every PHP upgrade, Python 3, etc). If Svelte is stable, they can signal that by keeping the version numbers stable.
People who are still considering adoption don't know enough yet to read release notes and understand what are breaking changes and what are not.
If you introduce a breaking change no matter how trivial or edge case it's considered WITHOUT bumping the major version number, I guarantee folks will be very bitter indeed.
Trust is hard-earned but easily lost. Best not to use a semver number blithely as a marketing tool.
Backward compatibility is best, but if you have to break things, make it 100% clear to folks downstream. This is what Svelte 4 did. The changes were mostly esoteric and changed a couple of defaults due to experience/lessons learned, but they were breaking changes made for good reasons. Leave semver considerations out of the marketing and concentrate on the problems you're trying to solve and how well the tool helps solve them for you.
"I don't like the way the garnish looks they put on my ribeye, so I'm just gonna head over to McDonalds."
JSX doesn't even parse the same as HTML5; it matches XHTML from decades ago. Again, the source doesn't match what the target uses (browsers). It's close, but not the same.
A Big Mac is close to a good burger, but it's not a good burger.
Hello everyone, hoping to make a few connections here. I'm a software engineer with 6+ years of highly focused work on UI and Front End related projects. React.js is my main UI framework currently, but have used Svelte and would love to more work in that area. I've also dabbled in some Back End technologies and I aspire to do more full stack eventually. Ideally looking for full time roles only, no contracts at this point. Thank you!
I've had a M1 mac mini for about a year now. It's been a really great machine, dead silent (never heard the fan), super fast and responsive. No complaints really, software mostly seems to have caught up to the new architecture. I do most of my work in JS/TS, React, etc. Don't know if I'd buy a M1 mac mini right now though, feels like a M2 refresh is due soon.
100% agree on the 1 hour maximum live challenge. As long as the challenge is relevant to the role being applied for, this is the way to go. This is enough time for the company to see some code and for both parties to ask questions about the tech, role, etc.
That hiring process doesn't sound too bad to me. I know some people are iffy on the take home portion though. I'm looking for work at the moment, 5+ years as a Frontend web dev. React.js, Typescript and lot's of good CSS skills if anyone is in need send me a message.
