Oh well, AI bros ruined it. I'm actually glad in some twisted way, because if more projects follow suit and close their development, it will again become an actual badge of honor to get on those teams. Having contributed to such projects will mean something.
I'm all for integration of system services if it helps bring a more cohesive OS. Interchangeability is a nice thing when building a system but I don't need it as a user.
No. From your tone it sounds like it's probably not as easy as you'd like. I don't really have a response to that. System customization is not something I'm interested in.
Can you share what was that thing that didn't work with systemd? I've seen pretty crazy setups and can't quite imagine how horrid of a mess those would have been if a large rc.init shell script ridden with sleeps was used instead.
Last time? Getting pppoe to automatically start and restart if it dies. Or not that, but setting up everything for a custom router with proper dns, firewall and all the other crap, without using crippled systemd versions for services that i couldn't even uninstall because of dependencies.
Maybe it's Ubuntu's fault since they seem to want to run in containers not on bare metal lately.
I've found JS/TS Web stacks equally lacking and ugly after Django. I'm totally spoiled by a decade in Django.
Just let me build a CRUD app, on the server, that spits out HTML without an excessive swamp of unmaintained nonsense and a cultish abhorrence of simplicity.
Try another language? The Go ecosystem tends towards libraries as opposed to "frameworks."
I personally chose C# for this reason, because ASP.NET is mature and (IMO) well designed. But there's also Java/Spring and and lots of other options in different languages depending on your preferences.
Well it might prefer libraries but the culture around basic DX things like ORMs is toxic. Just write the SQL yourself they say, until they themselves optimise to a half baked in-house ORM of their own.
I don't think I will ever understand the culture of Go. The syntax of a very low level language (needlessly verbose), combined with the performance of a very high level language (needlessly slow), with a bizarre aversion to any DX conveniences (pattern matching, ORMs, etc). If you're already giving up all that performance, why would you not take the extra convenience?
Not to mention that the demographic using Go - a simplistic-by-design, relatively slow GC'd language - is the last group I'd expect to get elitist about ORMs and demand every pound of performance from rawdogging SQL. That's a valid stance, but then why are you writing Go??! The common thread appears to be picking the most masochistic solution possible.
I can usually see the value of different languages for different use cases, but Go flummoxes me.
It was a mix of who came up with it, and having hit jackpot with Docker and Kubernetes rewrites from Python and Java respectively, into Go.
Had the rewrites not taken place, or Rust already being 1.0 by then, most likely would have had as many commercial success as Oberon and Limbo managed to.
You see this happening nowadays newer CNCF projects tend to be done in Rust, and there are even some that even go the C++ way, e.g. Envoy.
Judging by the community around Go, I also wonder if there's not an element of baby JS devs upskilling to Go, without yet having picked up a wider perspective. The performative aversion to DX could be explained if one sees Go as the opposite swing of the pendulum to JS and its excessive reliance on libraries, sugar, etc.
I'm aware of those platforms and have used them in the past. The tendency towards libraries is what bugs me. My preference would be a "Djan-go" framework, with the models, migrations, auto-admin, views, routing, caching, templates, all rolled into one cohesive framework that works out of the box. I don't want to make choices. I want to install it and start working.
Have never developed on/for apple platform, so I have no clue. Apple makes setting up development so hard, I wonder what motivates developers to jump through all the hoops.
> Apple makes setting up development so hard, I wonder what motivates developers to jump through all the hoops.
Money to be made. And they have (had) nice API for most development needs. The actual distribution is a arduous though, mostly around the Review process.
Taken to an extreme, what's stopping us from going back to C? The security issues will be found and resolved, performance will be great and it will compile on all platforms that ever existed.
Maybe it's just because I'm more of a SwiftUI person, but in the example on the homepage, the event == 'Cancel' condition seems like a strange and fragile way to check if a certain button was pressed...
reply