I'm not sure we have been living the dream with shitty desktop web apps running in a full browser each taking several gigs of ram for playing some music or chatting with coworkers and friends. Electron and its likes are the scourge of software world.
I'm happy if LLMs and the semiconductor shortage will create a renaissance of native applications.
> I'm not sure we have been living the dream [of software reuse]
But would you give up packages, central repositories, downloads that Just Work without patching, public version control systems, open-source software, ... , and much of what they enabled?
"Civilization advances by extending the number of important operations which we can perform without thinking about them." - Alfred North Whitehead, An Introduction to Mathematics (1911)
Getting packed into 2026 airline seats can be a "miserable experience". But that taken-for-granted human flight... a cramped seat in the effin clouds... is what? A century or two of focused effort, eventually massive effort, building that dream? Another century pursuing the dream of compact mechanical power? 10 millennia on metallurgy? So one's flight may have sucked, and there are many downsides to aviation existing... but living the dream of human flight, isn't living in a dream of no problems and effortless happily ever afters.
But yes, I'm so looking forward to agentic full-stack-ish rewrites, slashing through decades of accumulated stagnant cruft. Laptop-like angular-resolution HMDs are this-year-ish (though expensive, not mass market). And doing such rewrites by hand is a pain. Someone reports a Claude one-shot which installed a PICO Space Pro dev env, created a simple app, uploaded the apk to the headset, and responded with "ready for you to test"... and it was. Wild ride incoming. Though that's perhaps not a minimalist/efficient renaissance you had in mind? Still, in the midst of upset, there's opportunity to pursue visions which might not be viable in more settled times.
Ah. I was picturing downloading pre-autotools C programs. You'd ftp a tar file, find build notes or hopefully a Makefile... and watch the compiler errors go by. Seemed like everything was always written for some version of unix other than the one you had, or for a somehow different C compiler. Then you'd work the error list, translating library and system calls, tweaking C constructs. Eventually, hopefully, you could get it to compile, and maybe not segfault. Usually.
Later on, you'd hope the author created a `make.yourunix` or `INSTALL.yourunix` or README section for your unix, and that was nice. Then being able to simply say `./configure; make` and have it mostly just work... magic wonderful. Then basically "$ gimme name-of-the-thing", first for Perl, and then more and more others, eventually even python (but not C) - next level. And now we're at "Minion, build me an X", with an "and install whatever it is we need" implicit, quiet. That's, just, wow.
So from Objective-C and proto-C++ C-with-types, created hoping software might someday, maybe, be reused like hardware components... to now? So very living that dream.
And there can be fast paths. An electron app, watching evdev directly, full-screen under a generic X11 window manager, running 60 or 120 Hz or more, on a fast display or ignoring vsync, can be... sprightly.
The core of the problem is a profit incentive and an economy based on greed. Our society is designed to extract value, not to offer the best products/services to the general population.
The question is not about booting, it's about which OS is running the environment where development happens (writing code, compiling code, testing code, etc).
> Clarification: the operating system where e.g. your IDE runs on
If you're developing on a Linux VM that you connect to via a browser tab opened from your Windows laptop, you're developing on Linux for all intents and purposes.
That is, Windows was not doing enough for you so you switched to Linux for dev tasks.
By the same token, if your IDE is running in WSL, for all intents and purposes you're developing on Linux. A virtual machine, sure, but the virtualized OS is a Linux variant. Because installing the IDE on Windows itself was not doing enough for you.
I wouldn't consider Chrome the "operating system" that I am primarily developing on, even though it is really the VM under the hood. Windows is really the one facilitating running the Chrome application, or the Linux WSL application.
To be way too pedantic, if WSL2 (and therefore Hyper-V) is enabled then Windows actually boots into bare-metal Hyper-V first, which then launches the Windows kernel as a VM under itself, side-by-side with the WSL2 VMs if any are installed, so if the lowest level facilitator is what counts then you're really developing "on Hyper-V". I don't think that's a very useful distinction though.
I mean, that's a debatable definition, one could agree or not.
I program on Windows + WSL 2 e.g. and I have no idea how to develop on windows and barely used powershell in my life, but I know the ins and outs of Linux.
I'm not saying you're wrong and I'm right, I'm merely stating that we have different definitions and AFAICT there's no ISO standard saying what qualifies as developing on Linux and what not.
I guess it depends on what you do. I do python, rust, and web frontend in Windows. I have a personal bias against Docker, which'd otherwise be the primary WSL draw for me since if I want/need Linux, I can SSH into the majority of the machines in my house.
I'll throw out my unpopular opinion/experience here, too: I haven't liked any "desktop experience" I've seen or used for a Linux distro, and they all look and feel very similar to me: foreign, basic, and difficult for me to tweak and produce with. I greatly dislike the React stuff both on the web and in Windows, and use Classic Shell, which I'm satisfied with. Windows is easy to customize and almost everything can be tailored without even needing a reboot, many even with registry options already made and just waiting for a bit to be flipped.
It helps my puny, smooth brain, too, to just think of Windows being graphical and Linux being text-based; helps me remember what I'm doing.
Also my western Google pixel pro 9XL does not support it..while the Japanese version does. I guess google might be saving on the licensing or something.
Its also kind of bad form to scrape a huge website when there's a downloadable dump available. Save yourself, and more importantly wikimedia, a whole lot of bandwidth & CPU cycles.
You are correct. The core is Apache-2 and only lacks very obvious enterprise features. All the important CI bits are included in the Community Edition.
There is an EE edition in the works that will have a commercial license with more enterprise features like SSO, Okta integration, etc . I don't have the exact details but the license will allow small companies to use EE for free. The next step is to release EE.
It can be depending on the context (cultural genocide, for instance, often involves mass rape of native populations), but it isn't in this context - it's just mass slaughter.
...you just need to map keys. It was very easy, so now fn-arrow and fn-return work as a mouse on anything I've attached it to so far. I got an rpi recently, only connected this, and was able to navigate the startup ui with no mouse.
I think the biggest disadvantage to "do it in firmware" is it requires an external keyboard. (& the good ones which let your thumbs use more than one key are more expensive or diy).
Using the keyboard to drive the mouse isn't a nice experience. -- But, it's nice to have in situations like "I use a bluetooth mouse, on desktop, and bluetooth isn't set up/working". I've found that useful for live ISOs.
I'm happy if LLMs and the semiconductor shortage will create a renaissance of native applications.