HN user

andrewjf

416 karma
Posts1
Comments141
View on HN

This is pretty cool, it brings back memories. Thanks for posting.

I used to manage Tru64 (Alpha) and OpenVMS (VAX and Alpha). Mostly Oracle DB and whatever they called their App development suite (horrible, horrible software) for a University's ERP system (called Banner) and infrastructure (Multinet on OpenVMS/VAX for DNS, DHCP, mail, etc). After that I moved on to AIX on Power5 for Oracle on HACMP and Veritas Cluster. Such a different world from what we have now.

I have an old AlphaServer ES47 running OpenVMS and Power5 560Q running AIX in my garage

But you don't have to handle errors in Go. With multi-return you just don't bother with the "err" value and happily proceed with whatever is in the first return position.

IMHO, only languages with exceptions or Sum types that encode that a return is either a value or an Err (but not both) actually do what Golang says it does (make you handle errors).

The worst thing about UEFI HTTP boot is the utter lack of information to debug anything that's gone wrong. Whether that's the DHCP filename option is some wrong format for whatever stupid mode the UEFI is in, or there's some dhcp relay issue. It literally tells you almost nothing besides "can't get NBP file size".

The error messages seem to be written by people on a happy path who don't know how utterly broken almost everything about networking and DHCP even is.

And this is all IPv4! The IPv6 stuff is even more cryptic with different DHCP options and dealing with RAs and managed-flag, other-flag, etc.

It's infuriating. And I work on a team that writes code to generate all these things for automating bare metal for a living.

I agree with you, but haven't really left yet since there's still a good amount of discourse outside AI related topics. Seems a significant amount of contributors here are all to eager to fall over themselves putting themselves, their juniors, children, and colleagues out of work, long term.

I'm going to sound like a lunatic, but the best bug tracking software I've ever used was Apple's Radar internally. I wish they'd open source it. I've also had a bunch of fever dreams about re-implementing it as a product.

Quality in general seems to be going downhill, too.

Frequently the desktop app and the safari extension won't be in sync and missing a recently added password, or doesn't show up on my other devices hours later. I still have no idea how the extension vs desktop app actually work together, or if they do at all.

Sometimes 1password (safari extension) is "locked" - but the desktop app isn't locked? and No amount of clicking the little 1password icon, that's supposed to unlock it does anything. Just a completely no-op button. Quitting safari _and_ the desktop app seems to be what's required to fix it.

I've been thinking about just moving back to native macOS keychain, but I haven't bothered to check on linux+windows support.

I agree with what OOP said. But it’s not my intent to “shut sites down.” I have this view to try to increase diversity of media consumption and break people out of echo chambers. If your business model is so shit you have to exploit weaknesses in human brains to keep people viewing ads and can’t adapt, then that’s your problem.

If you have an algorithm whose sole purpose is to “engagement” with your own platform (by intentionally and purposely pushing clickbait, ragebait, and media that keeps reinforcing your clicks) you should no longer get section 230 protections - you are no longer a neutral party. These algorithms exist to create echo chambers and keep you clicking so you can consume more ads.

I would love to hear other ways of solving the problems of social media.

There's two kinds of reviews in my experience:

1. Does it work? Then ship it. This is great for early on, high-velocity where the goal is to get something working in the wild. AI and AI proponents love this option. It's easy to spot obvious problems, but very unlikely to lead to feedback on structural changes to abstractions and architecture to increase overall _long-term_ velocity.

2. We assume this works, but is it "correct"? This is where long-term code maintainability is created. The quality and effort put into a review like this is obviously far more involved than option 1. People working long term on a code base love this option.

We've been biased towards #1 for a long time, but I feel like we dont have enough people capable of doing #2.

I would be very happy to do so if we had working infrastructure, education, and health care not coupled to the generosity of your employer.

Isn’t it the case anyway that if you add state, federal, local, property, capital gains, and sales taxes, add the money that you and your employer pays for healthcare, that you’re basically paying slightly more in taxes all-in?

Sources on the first paragraph? I can’t tell what you’re even trying at say.

DACA (https://en.wikipedia.org/wiki/Deferred_Action_for_Childhood_...) was an exec order specifically because those individuals were brought over (as children, with no agency over their fate) after they were born, not before, so of course they weren’t citizens via the 14th. You’re correct that It wasn’t a law passed by Congress, but it’s irrelevant. I’m not sure what you’re saying, talking anything about DACA in this context is irrelevant.

Fair point! Makes complete sense.

But I wouldn't exactly call "professionals trying to make high brow media" exclusive alternative to Reddit, Youtube, Twitter, TikTok.

A lot of the propaganda (and sane washing) is coming from mass media, too. I feel like the only "legit" media outlets are like Reuters, AP, and some international ones, I guess.

That's really root cause in everything, isn't it?

- The consolidation of media (& social media in general) is about making money from outrage (emotions)

- Anti Vax (& other) movements is about people only receptive to people saying what they already feel (feelings)

- Accountability is gone because people care about being on the winning team and being "right".

Reason, Logic, and Evidence seems completely replaced by propaganda and mistrust of experts (fueled by the propaganda), but it's all rooted in comfort in people's own emotional validation.

Author argues against strong typing systems and language features to prevent classes of bugs and instead encourages developers to "writing lots of tests" for things that a type system would prevent.

The authors thesis seems to be that it's preferable to rely on the programmer who wrote bugs to write even more bugs in tests in order to have some benefit over a compiler or type system that can prevent these things from happening in the first place?

So obviously it's an opinion and he's entitled to it, but (in my own opinion) it is so so so, on-its-face, just flat out wrong, I'm concerned that that it's creating developers who believe that writing so many tests (that languages and compilers save you time (and bugs) in writing) is a valid solution to preventing null pointer defeferences.

You describe a world where human skill is required to prevent these class of bugs, time and time again we've proven that people are people and bugs happen.

Systems must be _structurally architected_ with security in mind.

Security is layered, using a random key with 128-bit space makes guessing UUIDs infeasible. But _also_ you should be doing AuthZ on the records, and also you should be doing rate limiting on API so they can't be brute forced, either.

I have two moonlanders but wound up giving up because I just couldn't adapt to it. And when writing code, finding the symbols like {, =, }, and other common coding ones was just too difficult to retain muscle memory. I tried many layouts, I tried to make my own, and at the end of the day it was just too different. I wish I had a better experience.

Any recommendations?

IPv6 Is Hard 1 year ago

I guess really the bigger issue here is the dynamic nature of the prefixes. If I could go log into IANA and click a button and get assigned a /48 then log in to my ISPs' sites and attach it to my connection and be on my way... I'd deploy it today, no problem.

Yes, this right here. It should work like a phone number where you can take it from provider to provider. You setup your gateway with your IPv6 prefix and then go.

Problem is all the technical and non-technical stuff to actually make that work.

- Verifying ownership of the prefix (rPKI or IRRs) and which ASNs are allowed to advertise it.

- Limiting allocations to someone? I guess phones solve this with SIMs

- Getting your ISP to route the traffic to your device

- Getting the device to announce it with RAs

- Dealing with asymmetric return routing over a slow "path" since it could be multi-homed

- Dealing with routing aggregation since IPv6 routing tables would explode with all the /56s in there

Maybe bring back Mobile IPv6? https://en.wikipedia.org/wiki/Mobile_IP

The one thing rants like yours completely ignore is that he’s not just “revealing”. But he’s taking action outside the authority of the executive branch and you people seem all too happy to cast aside rule of law for your own personal agendas.