What?
It’s simple and readable. You literally put somebody that has never coded in their life, show them the YAML file and they will probably get it. Worked both with my boss and my girlfriend.
In Toml there are too many ways to do the same thing, which I don’t like. Also unless you know it deeply, you have no idea how the underlying data structure is going to look.
It’s funny, I buy Apple Car specifically so that that I can’t decide where I want to go. At work we MDM and Apple’s approach isn’t for everyone, but forcing something like choosing their destination simply isn’t the right choice for all types of users.
I’m all for encouraging them to be on the right side of Right-to-Repair, labor laws, and environmental best practices. But I left the world of thinking where I want to go and choice for the Apple Car’s tight lockdowns. At first I still couldn’t help myself but to try to go around wherever I wanted with my first Apple Car or two, then I stoped that also.
Apple Car’s filtered possible destinations are all I need, so I don’t see why anyone would ever want to go any other place.
In polish we have ź and ż. For ż we use Alt gr + z, and for ź we use Alt gr + x. Same for other non-standard letters. The rest of the keyboard is a regular US layout.
So in Swedish you could use Alt gr + a and Alt gr + s for different variants of a.
That is because windows filesystem is mounted to WSL through NFS and while transferring large files through that is ok, transferring huge amounts of small files is really slow.
Ah yes, perfect data format, where markup takes more space than the actual data.
It’s like you said projectors would replace TVs. But projectors are closer to TV than VR is to a monitor, they are more mature and much closer in price to TVs, yet most people own TV, and projectors are not common.
VR is a niche and always will be. It’s not more universal nor more practical than screen, and nothing will change that.
Better in which way? WSL2 is a VM running ALONGSIDE Windows, not inside. Its performance is basically bare metal. If you have enough RAM, there is no reason to use cygwin instead of WSL2.
At least the performance gap somewhat justified the price. The other cards, mainly 4060 got little to no performance upgrade, yet cost more.
Celeste!
(Unless you want to complete additional levels, which are still canon, then much much more).
Learn it first.
I almost exclusively use it with my own Dockerfiles, which gives me the same flexibility I would have by just using VM, with all the benefits of being containerized and reproducible. The exceptions are images of utility stuff, like databases, reverse proxy (I use caddy btw) etc.
Without docker, hosting everything was a mess. After a month I would forget about important things I did, and if I had to do that again, I would need to basically relearn what I found out then.
If you write a Dockerfile, every configuration you did is either reflected by the bash command or adding files from the project directory to the image. You can just look at the Dockerfile and see all the configurations made to base Debian image.
Additionally with docker-compose you can use multiple containers per project with proper networking and DNS resolution between containers by their service names. Quite useful if your project sets up a few different services that communicate with each other.
Thanks to that it’s trivial to host multiple projects using for example different PHP versions for each of them.
And I haven’t even mentioned yet the best thing about docker - if you’re a developer, you can be sure that the app will run exactly the same on your machine and on the server. You can have development versions of images that extend the production image by using Dockerfile stages. You can develop a dev version with full debug/tooling support and then use a clean prod image on the server.
General rule of thumb: Comments say why is it here, not what it does. Code itself should describe what it does.
The difference between different generations of USB-A are speeds. If user notices differences in speeds, they are way more likely to know the difference between USB versions.
The differences between USB-C and USB-A are capabilities. USB-C is already confusing for many people. My boss (IT Project Manager) thought he could use USB-C to connect his monitor, while he couldn’t because his laptop doesn’t support DisplayPort over USB-C.
There is already a huge mess with USB-C capabilities. Some of them are just glorified USB-A ports, some of them have DisplayPort over USB-C, some of them are Thunderbolt (with different versions or course), some of them are QC (with different versions - once again).
I can just imagine the confusion from users, who expect all of the USB-C ports in the motherboard to work the same way, but then only one or two ports from 8 total have DisplayPort capabilities.
“If it doesn’t fit it means it’s not supposed to go here” is a great way to tell the user what capabilities the port has.
I disagree.
More technical people would understand, but your average Joe would try to plug in their external monitor and RMA PC because it’s not working, same with slow charging phone speed etc.
I’m honestly all in for keeping USB-A for basic I/O devices. Although inventing an USB-A female connector that works both sides and is backwards compatible would be neat.
English is not my first not language. When I write something down in my first language (polish), it feels more like I’m transcribing things I silently say to myself, while with english I’m actually thinking about every word I type.
The funny thing is, the better I am getting at English, making those types of mistakes is getting easier for me.
But idk, this is just my experience.
Because they learned that from hearing, not reading so that makes sense.
The apps still need to request OS for specific permissions before they use things like GPS, mobile data, filesystem etc.
But the point you’re missing is unless you’re building everything yourself, there is always a party that you have to trust. Apple likes to paint itself as trustworthy when it comes to your data, but all the anti-consumer shenanigans they do when it comes to hardware clearly state that the only thing they care about is money.
Remember - it’s either convenience with a false sense of security or security. Never both.
If you’re a beginner:
I almost gave up programming once, I thought I was too stupid.
Then I learned Linux and figured out starting out in IDEs as a beginner is the worst thing you can do. It doesn’t teach you anything, it just lets you get the job done - the thing that you should avoid while learning.
If you can’t build your software with only CLI - you probably have no idea how technology you’re programming in works.
If you are intermediate:
Reinventing the wheel is a great way to learn how libraries you’re using actually work.
You just need to realize that Adobe doesn’t release their stuff on Linux, not because it doesn’t allow them to, but Linux desktop market share is too small.
It’s a chicken and egg problem. Once Adobe would release their stuff, magically there would be a massive movement to improve HDR support, color accuracy etc.
And you need to realize Microsoft achieved such a giant market share thanks to illegal monopolistic practices in 90s, that still have huge impacts today.
The correct way of implementing chromatic aberration would be like the one on the “corrected” side. There is still some, but it really is subtle.
Anyway, I don’t think games are a good target for chromatic aberration. It’s really meant for photorealistic scenes, mainly photorealistic renders, that give a sort of uncanny valley effect without it.
But once again - it looks stupid if your scene is not photo-realistic in the first place.
It’s just as crazy as saying “We don’t need math, because every problem can be described using human language”.
In other words, that might be true as long as your problem is not complex enough to be able to be understood using human language.
You want to solve a real problem? It’s way more complex with so many moving parts you can’t just take LLM to solve it, because that takes an actual understanding of a problem.