This is why Java rocks with ETL, the language is built to access files via input/output streams.
It means you don't need to download a local copy of a file, you can drop it into a data lake (S3, HDFS, etc..) and pass around a URI reference.
Considering the size of Large Language Models I really am surprised at how poor streaming is handled within Python.
I don't think its aged well.
This game looked incredible for the time and introduced a rail gun sniper rifle you could one shot kill people with.
This map let you camp out and be a sniper but it was possible to overwhelm the sniper so the game stayed fluid and teams had to support their sniper.
Quake, HL2 Deathmatch, Counterstrike had similar weapons but quickly filled with people who could launch themselves 100ft in the air and headshot someone half a map away through a window which is why single shot weapons faded out of FPS games.
If you try multiplayer on some of these games, the skill level of opponents is even higher, they know every trick and execute them flawlessly. This destroys the reason the map was so good.
Playing the sniper in 4 player borderlands story is probably the closest you would get to the original experience.
Natural scrolling is the first thing I disable when forced to use a Mac, windows, gnome, kde, xfce, etc.. all scroll in one direction.
Macos has a unique keyboard and a lot of unique non obvious and non discoverable behaviour. For example I use a lot of windows laptops, left and right click involve pushing the trackpad downon the left or right. Someone had to show me right click on a Macbook was a two finger touch. These deliberate non standard behaviours make switching devices really annoying.
I would argue KDE defaults should follow the most common behaviour across multiple platforms, with the option to implement specific quirks.
The move to default double click brings the KDE default into alignment with other platforms (single click isn't the default anywhere else).
I would suggest a bigsur global theme that implements macos keyboard shortcuts, mouse actions, etc.. would be a better compromise.
I think its a self burn.
Person has never been in a relationship and so has no ex to photograph
Doesn't the fact you have to use a separate mouse tell you the design is poor?
The better approach would be to detect clicks on the left and right of the trackpad as left/right buttons and support two finger right clicking.
I have had a vareity of HP, Dell, etc.. laptops. The trackpads will do gesture stuff but you can clearly feel a left and right button if you push down on the trackpad (e.g. push on left side for left button).
Tesla actually market it as a positive.
Car manufacturers have to setup different manufacturing lines to provide different feature levels. Tesla argue this makes them more expensive. Tesla cars have all features installed, just disabled and the optional extra packages are cheaper compared to their rivals as a result.
To be honest there is a certain logic, if you've ever been in a Ford Focus LX (bottom range) its pretty clear they had to spend quite a bit of money on more basic systems. I honestly thought each LX was sold at a loss
I have a Mac book Pro for work.There is just a lot of random weirdness.
There is no right click, your supposed to do a light two finger touch for right click.If you click too hard it opens the dictionary.
If you plug in a mouse you can get right click, but it isn't consistent in working.
By default scroll is inverted (up is down, down is up), also windows can have scroll bars but they aren't clickable, you have to do a scroll gesture.
Almost every Left control + Button action is now Meta key + button. But not everything, its annoyingly inconsistent also new random shortcuts.
For example lock screen isn't Meta key + l like on Linux or Windows. Its Meta + Shift + Q, shut down is Meta +Left Control + Q.
The keyboard doesn't match the your countries layout, so keys move around and is missing traditional keys like print screen. To do that you press Meta + Shift + 4 to switch the mouse to a screen cut tool and select the area you cut.
I could go on and on, none of it is obvious and I wouldn't say any of it is an improvement at best its just different.
The admins to perform upgrades, monitoring, fixes, etc.. will require root access to the database. That means they can alter all your posts to say *blah blah blah" if they wanted.
Similarly passwords will be encrypted within the database and encryption algorithms have to be able to go in both directions. Normally they need a seed value to start random generation. The admin defines the seed as a result an admin can decrypt everything in the database.
@ergoplato I didn't suggest that.
Personally I don't think its ego. I think you have two issues.
The first is people go through stages learning DevOps. Stage 1 has people deploy a CI because its cool, they build a few basic pipelines and then 90% of people get bored. The 2nd stage is people start extending those pipelines, it results in really complex pipelines requiring lots of unique changes based on the opinion of the writer. You move to the 3rd stage when your asked to recreate/extend for a new project and realise how specific your solutions are.
Learning how to make minor tweaks and hook in a few key points to get what you want takes years. Without that most packagers will want to make big changes upstream which won't go down well.
The second issue, I have met quite a few developers who become highly stressed when the build system is doing something they haven't needed to do or understand.
A really simple example I have a Jenkins function which I tend to slip into release pipelines, it captures the release version and creates a version in Jira.
I normally deploy it first as a test before a few other functions to automate various service management requirements.
Its surprising how many devs will suddenly decide every problem (test failed, code failed review, sharepoint breaks, bad os update, etc..) is due to that function.
For me this little function is a test, if the team don't care I will work to integrate various bits. If they freak out, I'll revert decide if it is worth walking them through the process or walk away.
During the pandemic I had some unoccupied python graduates I wanted to teach data engineering to.
Initially I had them implement REST wrappers around Apache OpenNLP and SpaCy and then compare the results of random data sets (project Gutenberg, sharepoint, etc..).
I ended up stealing a grad data scientist because we couldn't find a difference (while there was a difference in confidence, the actual matches were identical).
SpaCy required 1vCPU and 12GiB of RAM to produce the same result as OpenNLP that was running on 0.5 vCPU and 4.5 GiB of RAM.
2 grads were assigned a Spring Boot/Camel/OpenNLP stack and 2 a Spacy/Flask application. It took both groups 4 weeks to get a working result.
The team slowly acquired lockdown staff so I introduced Minio/RabbitMQ/Nifi/Hadoop/Express/React and then different file types (not raw UTF-8, but what about doc, pdf, etc..) for NLP pipelines. They built a fairly complex NLP processing system with a data exploration UI.
I figured I had a group to help me figure out Python best approach in the space, but Python limitations just lead to stuff like needing a Kubernetes volume to host data.
Conversely none of the data scientists we acquired were willing to code in anything but Python.
I tried arguing in my company of the time there was a huge unsolved bit of market there (e.g. MLOP's)
Alas unless you can show profit on the first customer no business would invest. Which is why I am trying to start a business.