Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fl7305
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
151.
▲
by
fl7305
3y ago
That sucks. I can see how it costs thousands of euros per year to do the annual financial statements, but 15 000? Is that common, or were there special circumstances?
152.
▲
by
fl7305
3y ago
What does the opposite look like in Germany? Meaning, shutting down a Gmbh? In Sweden, you can get this done in a matter of days, where you sell the shares of your corporation for the net value minus a fee of about $1000.
153.
▲
by
fl7305
3y ago
> I tend to expect private individuals to seek targets with a higher expected value. If you're a very skilled and dedicated hacker, what other targets do you have that can net you many millions of dollars? > or an individual with
154.
▲
by
fl7305
3y ago
I'm not very familiar with CMake, would it be viable and better to change over to that?
155.
▲
by
fl7305
3y ago
I agree. The hack took someone with a lot of skills, determination and time. But doesn't that describe a significant portion of open source developers? There is also clear motivation. Wouldn't the exploit have been worth many mill
156.
▲
by
fl7305
3y ago
> might make that math (and whatever is needed to accomplish it) feel lot more worthwhile to actually-learn. I agree. Start with small hobby projects using what you already know. They should be things where you get immediate feedback, li
157.
▲
by
fl7305
3y ago
I'm not sure what the best solution is, but I agree on the pain dealing with autotools when they fail. Shotgun debugging where you start poking at things randomly can work for some stuff, but never works here. After working on many dif
158.
▲
by
fl7305
3y ago
All good things if you want to use the autotools. And other tools too. I've been porting and compiling Unix programs since 5 years before Linux. There was a lot of work needed to port between Unix variants, or even worse, non-Unix vari
159.
▲
by
fl7305
3y ago
Fear of heights is not the same thing at all as fear of flying.
160.
▲
by
fl7305
3y ago
> At some point I got upgraded to a Sun 3/160 on my desk I was going to say that it was a nice thing to have fall into your lap, but considering that it weighed 100 kg, maybe not. I got started with a Sun 3/50 when it was a few
161.
▲
by
fl7305
3y ago
> You can rename/switch branches. You can change what branch is considered main/master. Sure, in the project repo the branches are just simple text files that contain the hashes of the commits they point to. So they are trivial
162.
▲
by
fl7305
3y ago
Sorry, I didn't mean to sound disparaging. Given my specific use case of running compiled C code, then an advanced CISC CPU has a lot of wasted gates. But that's not what the VAX was designed for as you pointed out.
163.
▲
by
fl7305
3y ago
The heuristic would be "sound the alarm if the main branch is rewritten". And maybe also "if a release tag that we have used for our distro is moved". Wouldn't that catch most problems, and not generate too many fal
164.
▲
by
fl7305
3y ago
And what do office hours mean to a dedicated hacker?
165.
▲
by
fl7305
3y ago
I wouldn't make a Pikachu face if it was proven to be a major actor. But the "amazing patience" is not at all unusual among people who work on open source projects for fun, right? And what would the payday have been for a sin
166.
▲
by
fl7305
3y ago
If some commits are signed by people you trust, can the chain before that still be compromised?
167.
▲
by
fl7305
3y ago
That would be far from unlikely. But have we seen anything that would require more than a very smart individual with some time on his hands?
168.
▲
by
fl7305
3y ago
> there are plenty of legitimate reasons that program could fail to compile It's worse than that, these small C files are required to fail unless the target build environment meets some specific requirements.
169.
▲
by
fl7305
3y ago
You can automate checks for if a large part of the previous git history suddenly changed. You can't automate checks for malicious code.
170.
▲
by
fl7305
3y ago
Can you elaborate? Are you thinking of intentional SHA-1 has collisions? Would that work in practice?
171.
▲
by
fl7305
3y ago
> Are they 100% sure history was not rewritten at any point? With git, one way to check is if other people still have clones of the xz repository from a time when it was trusted. If you suspect the repo history has been tampered with, yo
172.
▲
by
fl7305
3y ago
> You might be thinking of the 785 Yes, I wrote that wrong. I initially checked the VAX wikipedia page and thought 784 looked familiar. But I'm pretty sure it was a 785 now that you remind me. > I/O was well engineered and w
173.
▲
by
fl7305
3y ago
Yeah, I think I remember seeing the sysops load the VAX CPU microcode using a floppy on the front panel (?) I don't disagree in general. Writing a disassembler must have been a real challenge. It's a waste of gates in the CPU. You
174.
▲
by
fl7305
3y ago
Thanks, looks like the VAX 11/750 was pretty much the same Dhrystone speed as an 8 MHz 68000 (Atari ST, Amiga). I/O and disk bandwidth is another matter of course.
175.
▲
by
fl7305
3y ago
In my circles, I think we just used the CPU name since there weren't that many of them yet, and unlike 386/486/586/etc, the 286 and lower CPUs weren't real 32-bitters. So, "386", "286" etc. Or ju
176.
▲
by
fl7305
3y ago
Wasn't VAX assembly very orthogonal and nice? I can understand if it was used as a compiler target, whereas x86 strikes me as harder to deal with? So if you have the space and free electricity in 1987, sure, give me a fast VAX. Not so
177.
▲
by
fl7305
3y ago
Yup. My point was that I can understand if someone rejects a 750 in 1987 because it is fairly slow. I think home computers like the Amiga and Atari ST had at least that much raw CPU power? But VAXen in general in 1987 weren't yet hopel
178.
▲
by
fl7305
3y ago
> And it's actually hard to do because you need to comb through the tree to update all the tags that point to the old commits. Isn't this part just a few pages of code, if that? I agree that it will be blindingly obvious for th
179.
▲
by
fl7305
3y ago
It's not that hard to emulate the basic Linux system calls. If you have the user mode compiler and libc running, then you can get simple console applications up and running in a day or two. Having looked at qemu a bit, it feels like a
180.
▲
by
fl7305
3y ago
A 750 wasn't very fast back in 1987 if I remember it correctly? But a 784 was still decent?
More ›