Yeah well you didn't include tan suit scandals so it doesn't count
neclimdul
joined 1 year ago
Once we had a "sr developer" join a project from a consulting group. The project wasn't going well so me and another dev started helping with some tasks as well.
After a couple days of helping, trying to get his web application to work with data from an API he turns to us and says "oh, json is just a string."
The other developer from our team stared at him for a few seconds, stood up, walked out of the room and told the project manager something along the lines of "if that guy ever comes back in the building I'll quit"
So yeah, json is just a string... But if that's the end of your knowledge you're in for a bad day.
Should I point out the irony of this complaint being posted on a site with ads every other sentence and doesn't even show what the windows ads looks like?
It's a valid complaint and all I just laughed as I scrolled past all the blank "ad here" blocks to read the article.
I really appreciate this change. Prior to it was always a struggle to deploy servers successfully. You'd reboot and your database would be on the wrong interface and you could even remote in because the management interface was suddenly on a firewalled external only network. Ask me how I know.
With virtualization and containers this just got more complicated. I would constantly have to rewrite kvm entire configs because I'd drop a new nic in the machine. A nightmare.
Sure, it's gibberish for the desktop user but you can just use the UI and ignore the internal name. Not even sure the last time I saw it on my laptop. So no big deal.
Libwebkit isn't actually chromium, it uses blink which is a fork of part of webkit. Understandable confusion though because webkit was part of kde, forked by safari, and then used by through chrome variants for a long time.
The rest of this comment is going to necessarily be nerdy Linux internals. sorry.
Unfortunately, I'm pretty sure chromium includes it inside it's binary and does provide or use any webkit libraries.
Orca uses it internally for it's browser so it won't start unless it has access to the library. When you build a Linux app it includes the name of the library which includes the ABI (basically the version). Newer Linux release include a different version.
You can see how that specific library stops appearing in Ubuntu releases https://packages.ubuntu.com/search?keywords=libwebkit2gtk-4.0-37
The new version is 6.0 I believe.
Appimage is one of the ways you get around this distro problem by including the versions of libraries. That's why they're so big. There are problems with that like how big the apps are stale bundled libraries with security issues but I digress.
Orca hasn't bundled webkit in the appimage and because of another problem/feature of appimage it falls back on the os library. Since new distros have dropped the older obsolete library version orca can't start.
That's a lot but I hope it explains the problem better.
I would like to help but my personal computer doesn't currently have enough memory to compile orca so back to just watching warning people it's a coming problem for them too.
That's good. I assume you've got the old libwebkit installed somehow. There are a dozen reports around this though so it's a pretty real problem. https://github.com/SoftFever/OrcaSlicer/issues?q=libwebkit2gtk-4.0.so.37
Ubuntu but it also affects fedora https://github.com/SoftFever/OrcaSlicer/issues/185
The image just isn't being built correctly which is more a problem with appimages but the fact it's still broken... Linux is clearly a neglected platform for them.
All the problems I listed have bug reports just nothings happening to fix them.
It was actually 3gb because operating systems have to reserve parts of the memory address space for other things. It's more difficult for all 32bit operating systems to address above 4gb just most implemented additional complexity much earlier because Linux runs on large servers and stuff. Windows actually had a way to switch over to support it in some versions too. Probably the NT kernels that where also running on servers.
A quick skim of the Wikipedia seems like a good starting point for understanding the old problem.
Appimage doesn't start because it relies on a system package that does exist anymore, dialogs with grey text on grey backgrounds in dark mode, stl repair not included...
Flatpak is in the works but honestly and hope that helps bit I get better prints out of prusaslicer for some reason so not holding my breath or anything.
Does it work on recent Linux releases yet?
It is. Until recently it actually still used the domain to serve assets.
"I know what a lot of you are thinking" Yeah what about Firefox? "It's impossible to make a new web engine" Um... No ... Probably not that hard really with pretty decent standards these days. Performance JavaScript is probably pretty hard and a lot of the fancier protocols.
Seriously, what makes you better than Firefox?
Whatever, another choice isn't bad I guess.