A new era of productivity tools by Microsoft is needed. All of their current tentpole products are just web versions of their old apps, and most of them are very annoying or slow or just weird. I'm intrigued to see where this leads as they double down on their web-first strategy.
As for the Wave comparisons, it's more of a technical comparison of the Fluid framework and Wave's real-time collaboration data model/editor, right?
> and most of them are very annoying or slow or just weird
It's kinda mindblowing that in $CURRENT_YEAR we're able to do run beautiful-looking ray-traced video games on a home console that costs a few hundred dollars, but when I launch Microsoft Word on a several-thousand-dollar MacBook Pro it takes over 8 seconds from a cold start (just timed it right now).
We've all just accepted that 8 seconds is an acceptable time to wait to type some words into a computer.
I knew I saw this on HN a couple days ago. I figure that's what "inspired" this article, though it doesn't really have any more detail than the tweet thread...
I bought a physical copy when it was released a couple of years ago. I've recommended it a few times; I think it's worth reading for anyone who hasn't spent much time writing actual mathematical software or hasn't had a formal CS education.
I think you're thinking of Next/Nuxt. I'm a laravel dev but have tried every framework under the sun cause I get bored.
Next/Nuxt are basically react/vue SSR / Server Side Rendering or SPA frameworks... which seems more like Angular..no?
Nest.js is a fullstack backend framework more like fastify or express and has guides on connecting databases, graphql, etc....
Personally, if I were going to go with node, I'd choose nest.js or feathers or express as they have the best ecosystems ... but none seem as mature as laravel, rails, or django.
Maybe they were inspired by the way it was built/laid out, but angular is more in the vein of react/vue.
Nest.js is more like feathers, actix for rust, flask, lumen, etc... it's not as opinionated iirc last time I played with it... so there's not a specific way everything is organized like a rails or laravel project... if I were doing node it'd probably be nest, but w/ swoole/octane and knowing laravel inside/out I'm gonna lose time/productivity switching to anything else, so I stick w/ what I know.
ChromeOS's Linux support is even more streamlined than Windows's approach. You enable it, the container is automatically created (though, it is possible to install other distros -- but you void official ChromeOS support), and then graphical apps just work. All window management works across Linux, Android, and ChromeOS apps seamlessly, and even the open with dialog in the ChromeOS file manager shows apps across Linux, Android, and ChromeOS. The app launcher also includes Linux apps.
One unique "feature" I like about the setup is how easy it is to just delete the container and start-over if I'm so inclined. I have an elaborate set of scripts to bootstrap a newly created Linux container on ChromeOS -- if anything goes wrong, I can just delete the container and re-run the bootstrap scripts.
I'm a big fan of where ChromeOS has headed and I like the containerized approach to the problem a lot. It's extremely close to getting to the point where I'd consider ChromeOS over MacOS for a work laptop, especially since they added Desk/workspaces support. I use ChromeOS exclusively at home and for personal dev now.
I'm kinda curious if in some wild future WSL3 ends up being Windows completely ditching the NT kernel for linux kernel and building up wine to be a first class Windows API emulator.
It's just increasingly silly in the Azure and server space to be running Windows--you lose all the benefits of the container ecosystem and have all the baggage of decades of windows cruft (yes I know windows containers exist--no one uses them). Desktop usage has been in decline forever and I have to imagine they could get the 90% of windows API apps left that matter to work great on wine. It would give Microsoft a huge boost to get back in ARM by building on the linux kernel and its great support vs. windows ARM very limited set of qualcomm and a handful of other chips.
AFAIK Windows is still one of Microsoft’s golden geese. If they transitioned to Linux, they’d lose out on all that sweet, sweet licensing revenue. Which makes this seem unlikely to me.
Last I heard internally there hasn't even been an official Windows OS team for the last couple years after Myerson left. It's been divvied up and split apart into parts of Azure, etc.
Yes, technically it is, but it's the integration that makes it interesting.
Plus theres the simple reality that Microsoft's got native APIs in Windows that enable running a linux vm with a KDE window alongside the standard windows environment. Microsoft has really come a long way and that's what's really amazing and kind of disorienting.
WSL2 uses it's own init system - only one kernel (plus a tiny initrd) is virtualized by hyper-v; each subsequent linux instance (distribution) is containerized. There's additional facilities that handle resource allocation dynamically vs the user specifying a static amount during VM creation.
These (and more) result in the end-user interacting with WSL2 the same way they would any normal application. To think of it as simply a VM isn't quite correct.
So I fired up Ubuntu first for my current WSL2... then I installed a Kali distribution.. are you saying that the Kali instance is really just a container inside the Ubuntu WSL2?
Not quite. WSL2 dynamically uses resources as needed (`vmmem`), whereas a traditional VM requires allocating a fixed amount of RAM and CPU from the host machine.
While it looks dated, SL has a far more intuitive UI, in my opinion. I don't recall any major issues with this release. It seemed to "just work." Big Sur seems like a toy by comparison.
An anecdote, I still remember installing Snow Leopard on my Polybook; it was the first OS update since switching to a Mac. I received the physical delivery since it was still distributed by disc, so I left my house. I was able to install it a few hours later while waiting on an appointment sitting in the car, all while on battery power! It was like magic.
I actually like the look of Big Sur, but the bugs... oh god the bugs.
That new notification center looks real nice. Shame my first experience with it has been it repeatedly hanging, gobbling up RAM and CPU cycles, and generally not displaying notifications.
(Extra fun if it hangs while notifications are still on screen; then they just sit there forever. 'pkill NotificationCenter' has been my friend lately.)
It’s kind of interesting because in the Snow Leopard era you didn’t have OS level notifications but you had Growl. And the Growl API was extremely well supported, and arguably better supported because it wasn’t limited to App Store apps.
Further, Growl allowed the user to customize look and feel, persistence, the types of notifications, etc which allowed you to create a notification system that was far more effective than anything available on the Mac today.
It’s easy to argue that 12 years later notifications on Macs is worse than what it was in the late 2000s.
Agreed. It’s an odd thing to say, but I’ve been using Macs since the early days, and something about SL felt like OS X had finally arrived—like the platform had reached the point where Apple wanted it to be.
Not that the earlier versions were notably bad or anything, but something about them still felt new and experimental. I remember thinking Snow Leopard was the point at which X graduated to “the new normal”, for lack of a better way of putting it.
I agree Big Sur is a big step back. They've changed all the icons in System Preferences again, and the new sound-levels UI in the menubar is very confusing.
This is a handy tool, big thanks to the dev who put this together. This is going to be an excellent educational tool. My only suggestion I have is to add links to the docs for the detail page's relevant function.
