aeruder

Missouri also has a governor that vowed criminal prosecution for a newspaper reporter who discovered “View Source” on a state website revealed teachers social security numbers [1]. This went on for months.

Even if a white hat had discovered flaws in Jackson County, they’d have to be insane to do anything with that information.

[1] https://missouriindependent.com/2021/10/14/missouri-governor...

Actually just saw news that they’ve wrapped filming on season 2 of Silo and they’ll be airing 2025. :)

I really like how well the pattern-matching system in Elixir works with decoding binary data. It can even extract on non-byte boundaries.

Large parts of the ziprecruiter website are still powered by perl.

Chicago

Yea, just to be clear though: Asahi Linux still works pretty well. My system boots near instantly; wifi, mouse, keyboard work fine. Its enough where I can easily use my M2+linux as my daily driver.

This article is addressing misleading comments that made it sound like everything for apple silicon was merged into upstream kernels. It's not. You're still going to need to use Asahi kernels and userspace bits for a while.

Sad, but I would occasionally use my "unlimited" PTO to take a week off and just get work done. Most of the pain started when we transitioned to a sprints from a lack of process. In theory, this was to make things faster (which actually most of the reasons we were so slow was unrelated to process). My week suddenly went from getting things done to:

- 60 minute meetings fighting over whether tickets were 3 or 5 story points

- turning our entire process into some kind of perverse waterfall method where stories involved days of prep work defining every step so that we could accurately estimate story points (I thought this was the opposite of agile?)

- offers to "help" from project managers and managers when things took longer than expected - this help took the form of additional meetings.

- absolute inflexibility over my noon standup. I could be in the deepest of zones and people would literally slack repeatedly until you showed up for that thing

Cue the "oh you were doing <X> wrong!!" people. Modern software practice sucks. Its fine for small bugs and very well defined tasks. Outside of that it is just interruptions, interruptions, interruptions.

I also ended up just quitting. New place is better, but still in many ways the same. At least here I don't have comparisons made to my old days of the pre-software-process productivity.

100%. I worked at a company that really went in hard on Agilent Vee for hardware testing in the early 2000's. Absolutely a thing where a manager saw a "Hello World"-like demo and was so impressed that they went 100% full buy in.

Besides the obvious UI issues (like the fact that you couldn't really zoom out, you could just pan around your code), we had a bunch of engineers that still needed to do things like "get the three largest values from this array" and it just turned into the most ridiculous bubble-sort implementation you've ever seen.

Its pretty hilarious seeing some of the old screenshots now [1].

Anyways, I think it will always be really easy to sell some simple demos on low-code/no-code, but then the second you need something slightly outside the eco-system it just turns into a substandard mess that doesn't work well with source-control (or diffs) and in general is just harder than the code-full solution.

[1] https://i.imgur.com/KsVliNE.png

I worked for a company that used A/B testing to justify call-to-cancel; makes me angry every time I think about it. I guess that's one of the tricky things about A/B testing - it is easy to measure that call-to-cancel decreases customer churn, not so easy to measure the number of people that will never sign up for your service or the number of customers that do churn and swear to never use you again.

Still makes me mad. I bought a device that plays PS3 games and runs Linux and then Sony said I have to choose.

IPV6 can cause some issues around this because browsers will typically do an IPV4 and IPV6 lookup in parallel. Try adding a

    ::1 youtube.com www.youtube.com

also.

In California it is illegal. If you work in trendy software companies, startups, etc - it probably isn't common because so many people have Githubs.

As a embedded software engineer, I've had specific language claiming rights to everything (one even called out "songs or other copyrightable works") I do while employed at the company at 4/4 of my post-college jobs.

The trick here is that each byte is treated as a signed 8-bit number. When the top bit is set, the number is negative.

> They also run the risk of being held personally liable if someone were to be injured by the pothole they attempted to fix.

Are they suggesting that the city can be held liable when a pothole they _haven't_ fixed jacks up my car or its tires? I've not really heard of that working in practice. From Portland's own website [0]:

> Most pothole claims are not paid.

Yea, figures - I think I'll take my chances with the anarchist-repaired potholes.

[0] https://www.portlandoregon.gov/bibs/article/629953

Or they could just sign up at one of the numerous free email providers with a different username. Stripping the + suffixes is only providing one thing - pain for the users that want to use it.

Understood, and I totally agree that it is an industry ready for some shakeup.

I used to work for a large defense contractor doing FPGA work, and we really went out of our way to try to stick to 100% VHDL to attempt to avoid vendor lock-in. This meant things like writing block ram HDL in a way that it would be inferred by the synthesis tool to use the block ram (and not synthesize out of a bunch of LUTs).

It was a constant struggle to keep things synthesizing correctly. We mostly standardized on using Synopsys Synplify Pro for vendor-neutral synthesis and then using the Altera/Xilinx backend tools for place and route, etc. But even then, we regularly had to whitelist certain good versions of Synopsis' tools.

It was possible to do this with the vendor-specific synthesis tools too, but it was still a massive effort to check that primitives synthesized into the correct elements across different parts/vendors. Ugh, do not miss it.

C (or really any traditional programming language) doesn't really map to an FPGA. There are some compilers out there that attempt to convert traditional C code to state machines for FPGAs, but FPGAs are really a completely different paradigm. You're actually describing digital logic, not a sequence of steps.

That being said, there are soft-processors that have been written in VHDL/Verilog and can be incorporated into a FPGA design, and those CPUs do often have GCC support (Microblaze Xilinx, NIOS 2 Altera, plenty of MIPS CPUs out there, etc.).

I don't understand why they go through so much effort to churn out these boards that are made useless by lack of upstreaming.

Oh, wait, because idiots like me keep buying them and finding this out too late. Thanks for saving me $20 this time.

100% correct. Far too many misinterpretations of the LGPL out there seem to ignore the requirement that the LGPL'd portion must be able to be replaced/updated.

I've seen way too many LGPL-licensed embedded-C libraries and VHDL libraries where it just does not make any sense. If your target platform doesn't have a dynamic linker, then LGPL is the same as GPL. There are some hacks where people distribute unlinked .o/.obj files. This is acceptable as well, but I don't see it too often.

Make unfortunately depends on hard-tabs for the recipes. Your editor probably switched it to spaces.

An article about the "attrs" library was posted here a couple weeks ago. Really highlighted the tedium of Python objects while offering a neat solution.

https://glyph.twistedmatrix.com/2016/08/attrs.html

Regarding protobuf, I'm a bit disappointed with the direction of version 3. Fields can no longer be marked as required - everything is optional; i.e. almost every protobuf needs to be wrapped with some sort of validator to ensure that necessary fields are present. I understand the arguments, but I did enjoy letting protobuf do the bulk of the work making sure fields were present.