Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
qalmakka
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
48 ms
·
601.
▲
by
qalmakka
5y ago
Sometimes I forget how insane Perl was before `use strict;` became commonplace.
602.
▲
by
qalmakka
5y ago
I hope Apple will be punished for their behaviour. I could ideally understand them reserving the power to decide what gets uploaded and what doesn't on their stores, but then they must allow sideloading. People paid good money for thei
603.
▲
by
qalmakka
5y ago
Short circuiting for logical operators has existed at least since the first C versions in the early '70s. It's maybe not intuitive, it's probably a crummy idea, but that's how basically everything based on C works (inclu
604.
▲
by
qalmakka
5y ago
This is uttely false. I desume you haven't used C++ in the last 10 years, or at least you didn't delve deep enough into it to really understand how powerful (while bonkers) the C++ type system is. C++ has a much, MUCH more stronge
605.
▲
by
qalmakka
5y ago
Well the fact you couldn't reasonably use arrays without Generic Const hit stable in Rust 1.51 says otherwise. Defining templates on values is very useful, especially in C++ where you can provide template specializations. You can do a
606.
▲
by
qalmakka
5y ago
> you might want the behaviour shown here of not short-circuiting. Or you might want to create a bitwise function that also allows calling on single-bit (i.e. boolean) values. In both cases, I think the risk-benefit ratio is way too skew
607.
▲
by
qalmakka
5y ago
The fact implicit conversions exist doesn't really weaken the type system, the two are different concepts. If you define an overload or a type specialization on both the compiler will call the right version without any ambiguity. You c
608.
▲
by
qalmakka
5y ago
If you stop integer values from being implicitly convertible to booleans, you break the language and its compatibility with C. The inverse is debatable, though. I honestly don't see why someone would do bitwise operations on boolean, u
609.
▲
by
qalmakka
5y ago
C++ definitely hasn't a weaker type system than "newer" languages like Java - if any, it is much more richer and complex than most languages out there. What's happening here is a type conversion that has to be in place d
610.
▲
by
qalmakka
5y ago
If I think about it I've always instinctively associated unvoiced sounds like /k/ and /t/ to sharper shapes, and sounds like /b/ or /v/ to "rounder", softer shapes. I think that voicing
611.
▲
by
qalmakka
5y ago
I've had to fix more broken JSON files with fancy “„ than I'd like due to people attempting to edit them with Word, so I must say, you have got a point.
612.
▲
by
qalmakka
5y ago
Uh, so that's the trick, very neat.
613.
▲
by
qalmakka
5y ago
Wow, I always though this was unfeasible due to how limited the ESP32 MMU is.
614.
▲
by
qalmakka
5y ago
XML has always felt to me as both a great and a terrible idea, at the same time. The fact it's built around schemas is great, and this makes it way better at representing serialized structured data on a file than JSON and anything sche
615.
▲
by
qalmakka
5y ago
It's QEMU and the kernel that do the magic - libvirt is actually kinda annoying and ill suited for these things, you have to edit lots of unnecessary XML just to change launch options for QEMU.
616.
▲
by
qalmakka
5y ago
Thanks for your explanation, now it's much clearer. It puzzles me why NeXT went through the extra effort of patching OSFMK instead of just doing like everybody else was doing and just fork a monolithic BSD kernel - probably they were a
617.
▲
by
qalmakka
5y ago
Wasn't Mach a re-implementation of the original 4.2BSD completely based on IPC in place of syscalls? I distinctly recall some documents saying that XNU achieved much better performances than plain OSFMK thanks to NeXT reworking the BSD
618.
▲
by
qalmakka
5y ago
Yes, but I really don't see the usecase for letting something potentially remote and untrusted to a serial device. How many people do actually need that? (Limited) filesystem access for web applications is also kind of dubious, outside
619.
▲
by
qalmakka
5y ago
Who thought that an API to connect to serial devices from browsers was a good idea? It seems kind of dangerous to me.
620.
▲
by
qalmakka
5y ago
To me, this sounds kinda like the following: - XNU was born from a fork of the Mach microkernel - When the microkernel hype simmered down due to them being way too slow for '90s machines, NeXT bolted on lots of chunks taken from BSD to
621.
▲
by
qalmakka
5y ago
I think that the MPLv2 covers the best of both worlds. It is a lightweight copyleft that requires you to give back the modifications you do to the original codebase, but it doesn't prevent you from static linking or mixing code with ot
622.
▲
by
qalmakka
5y ago
This is very cool, I'd like to see more projects using libgccjit because it's much, MUCH nicer than the usual approach of building your frontend alongside GCC. I think it's the first step towards a modular GCC, which is an ab
623.
▲
by
qalmakka
5y ago
One big issue with this is that Microsoft has supported BIOS/MBR for way longer than it was needed - "MBR" is a legacy from the past, and having an executable UEFI bootloader in a GPT ESP is so vastly superior to just loading
624.
▲
by
qalmakka
5y ago
Windows 11 is quickly shaping to become the new Windows 8 or Windows Vista (or a Kinect-like fiasco). Microsoft risks losing mindshare on that segment of "technical-but-not-really" people that actually recommend and spread opinion
625.
▲
by
qalmakka
5y ago
I agree. No matter how much Microsoft tries, given they can't remove local accounts altogether I will refuse to log into a Microsoft account for as long as it is humanely possible. Same for secure boot.
626.
▲
by
qalmakka
5y ago
Hmm, they are tolerable to say the least. I think lots of people complaining with bad compile times are probably developing on underpowered laptops, which are definitely not the right tool for C++ development. I've never had an issue o
627.
▲
by
qalmakka
5y ago
Null terminated strings are the root cause of millions, if not billions of security vulnerabilities caused by buffer overflows. All modern languages have shunned null-terminated strings in favour of something in the likes of struct stri
628.
▲
by
qalmakka
5y ago
Because it's a hassle, and I really don't care about that. Given that I'd have to go through the hassle of signing my own kernels just to get Windows to boot once a week, I really don't get why I should do that in the fi
629.
▲
by
qalmakka
5y ago
If you can't boot Windows 11 without having secure boot turned on, I guess I'll have to skip this Windows version for the first time in decades. I've always been an early adopter for new Windows versions, but I really can
630.
▲
by
qalmakka
5y ago
So Microsoft has chosen to go down the Windows Vista route again. People are notoriously reluctant to update Windows, and if they really want to start this early with FUD about their next OS, it's very likely it's going to be reje
More ›