I’m a staff software engineer at Sunrun, the USA’s largest residential solar installer.
I mostly work with kotlin, but also java, python, ruby, javascript, typescript. My hobby is picking up new hobbies. Currently bird photography and camping.
But that could easily be due to the quality of the projector rather than the resolution. Everyone in here saying they notice differences is completely missing the point. You’d need to compare against the exact same panel type, manufacturer, model year, etc with the exact same manufacturing processes in order to come to this conclusion yourself.
our black cat once ran under the ladder of a bunk bed, crashed into a mirror leaning against the wall, causing it to fall against a shelf and knock a salt shaker off (we were in college, gotta keep your food stuff in your room and whatnot). The mirror crashed to the floor and broke. We didn’t believe in curses and that fully cemented that belief for us.
all they need to do is get you to install a sketchy browser extension and then anytime you generate a password on ddg they’ve captured it. No man in the middle necessary. Unlike generating a pw with your pw manager, then inserting it with your pw manager or just typing it into the field (which shouldn’t be accessible to extensions on any appropriately coded site).
The HN comments are full of people discussing how to get around the software. This is why it costs so much to run programming.dev. People that think the cost of information should be free and that anyone they want info from should bear the cost of giving them that info.
with fzf you get better grep with fuzzy search
works in fish shell as well.
I struggled with WinApps as well. wasn’t ever able to get gpu passthrough working either, and trying to do so really destabilized my computer. I pretty much gave up. That’s not to say that WinApps doesn’t work. It does, it’s just not near native for me. There’s definitely slowness, at least with Lightroom, I haven’t tested with PS yet, though I have installed it.
Yeah defining an announcement of something as its birthday is weird. I’m also biased on this, cause it came out on my birthday.
about 50% of traffic to programming.dev is bots who have marked their user-agents as such. I’m pretty confident the actual number is higher, but haven’t spent time validating.
as an instance admin I will let you know that lemmy (the software) runs very very poorly.
buying a pan increases demand for that item, which then gets built in those factories that then pollute the water you drink and the air you breathe. So yeah, they’re directly correlated.
recent studies have stated that the pans offgas from manufacturing for weeks after you’ve bought them, no heating needed, so no, that’s not correct. and it was known that they offgas at only 325ºF years ago. https://www.ewg.org/research/canaries-kitchen
so no, teflon pans are bad no matter how you use them, they’re bad for the environment, they’re bad for your health, they’re bad for animals, they’re bad for babies that haven’t been born yet.
using a pan means you have to construct that pan, in a factory that pollutes massive amount of PFAS directly into the soil and water table.
android studio is built on intellij, and as a result can do the exact same things intellij does, which includes the .http files (which I think are the same as .rest files). So you can get the exact same features in android studio as you do in vscode. I think.
wait… are you arguing that gems are a bad thing???
Wow. Yours looks really clean. We have two of these drawers and they’re maxed out double as full.
when the official docs are telling you to use it, then it’s used. You can have no expectation of people to think the tooling isn’t shit when it’s literally the official recommendation.
Forking is a foolish idea. The core principle of computer-science is that we need to live with legacy, not abandon it.
what a crazy thing to say. The core principle of computer-science is to continue moving forward with tech, and to leave behind the stuff that doesn’t work. You don’t see people still using fortran by choice, you see them living with it because they’re completely unable to move off of it. If you’re able to abandon bad tech then the proper decision is to do so. OP keeps linking Joel, but Joel doesn’t say to not rewrite stuff, he says to not rewrite stuff for large scale commercial applications that currently work. C clearly isn’t working for a lot of memory safe applications. The logic doesn’t apply there. It also clearly doesn’t apply when you can write stuff in a memory safe language alongside existing C code without rewriting any C code at all.
And there’s no need. Modern C compilers already have the ability to be memory-safe, we just need to make minor – and compatible – changes to turn it on. Instead of a hard-fork that abandons legacy system, this would be a soft-fork that enables memory-safety for new systems.
this has nothing to do with the compiler, this has to do with writing ‘better’ code, which has proved impossible over and over again. The problem is the programmers and that’s never going to change. Using a language that doesn’t need this knowledge is the better choice 100% of the time.
C devs have been claiming ‘the language can do this, we just need to implement it’ for decades now. At this point it’s literally easier to slowly port to a better language than it is to try and ‘fix’ C/C++.
I mean sure, but you can say the same about any resolution possible. At some microscopic distance on a 42k display you will be able to see the difference. Your scenario here is pretty much “if you use a display in a manner it wasn’t intended then you’ll be able to see the difference in resolution when you compare it to a display that is used in the manner intended”