artisanspam

The marketing culture for announcing hardware exploits is so strange to me. The norm seems to be getting a custom domain, logos, demos, an FAQ... why do all this instead of just reporting the exploit and releasing a paper?

Readwise Reader. Yes, as another commenter stated it costs money, but it has many other features that I find useful such as good text-to-speech, integrations with other apps like Obsidian, and a good export feature if I want to switch to another feed app.

I love RSS. I use RSS daily. I use link-aggregation websites like HN to find interesting authors and subscribe to any RSS feeds that they have. Highlights from my reader sync automatically into my Obsidian vault. It's great.

But I know I, and everyone else posting in this thread, are in the minority. It's clear that most people prefer algorithmic drip in a walled garden. There's a reason everyone flocks to those platforms when RSS superseded them. I don't think I need to re-hash why those platforms are bad for the health of the internet and society as a whole.

So what can be done at a structural level to fight this? What can be done to incentivize people to leave these algorithmic drip feeds to reverse this trend?

I primarily write code in a DSL which has no good FOSS LSP implementation. If I’m writing this code on my personal computer I’m out of luck. My employer pays for a language server that requires a license.

There are a non-negligible number of my coworkers who don’t use the licensed LSP implementation and they write all their code in vim – or worse, gvim through a VNC. It’s very easy to tell that their code quality is worse.

Because I am not always driven to type 128 random characters or even use my phone camera, so it does successfully stop me from procrastinating much of the time.

You can make it up to 128 characters. That's impressive that you are able to type a random string of nonsense so fast.

My hack was to take a picture on my phone, have Apple's image recognition copy the string to my iCloud clipboard, and I'd paste it on my mac.

It's too easy to defeat the purpose of these things if you're even slightly driven.

That’s the ideal but it’s not what I’ve observed in practice. In my org, people send reactions and reply all emails like this. It’s just more distraction.

I do really think that PG often glosses over what he really means when he says "success." From a critical view, you could interpret the word to mean solely financial/economic success. Given his occupation, I would imagine that's his intention with the term.

But if you replace that term with something like "virtue" or "eudaimonia" and read from that perspective, there can sometimes be some truths to glean from his writing. Nothing really novel, but interesting to read nonetheless.

> The easiest way to improve this would be to capture as much of the architecture as possible in formats that are easy to read and manipulate. In particular, instruction encodings and control/status registers are easily described by simple JSON/YAML/XML/… formats.

This has been something I wish was available for ARM pseudocode. It’d be ideal to just generate an equivalent Python, SystemVerilog, etc. library from the ARM ARM instead of having to reimplement a subset of it yourself.

I am a DV engineer, and I'm going to give some candid feedback: CI tooling is not what I spend most of my non-coding or verification-planning time on, so I wouldn't find much use out of this tool. Now that wasn't always true – I used to work somewhere that had horrible CI tooling. But that's just because the company didn't invest in someone to maintain that infrastructure. Given that, I don't think they'd pay an external vendor for a tool and require someone to maintain that tool as well.

However, I do have some problems that you may want to consider pivoting to or adding in the future:

1. A wrapper that works with all of the tools that EDA vendors offer as a back-end. Basically, CMake for SystemVerilog where I can just run `make` and compile, elab, and sim run in order. Every company I've worked for has made their own wrapper program which essentially re-creates this process and I've had to relearn it several times. If you had this wrapper, then you could easily just use other CI/CD pipeline which calls this tool. Bonus points if you can integrate it with VUnit or SVUnit unit testing frameworks.

2. SystemVerilog code generation. Something smarter than just "I wrote a Python script that prints SystemVerilog code to a file based on some config file and then you run your build with the file the Python just printed."

I'm sure there are others that I am not thinking of. But overall, I don't find a lack of CI to be the problem. It's the lack of tools that a CI pipe uses that's the problem.

ETA: Also, was it intentional to launch right on the tail of DVCon? If so, clever planning.

It's not just Ubuntu. Anyone using Centos 7 or RHEL 7 which are not EOL yet has run into this issue, too.

The Ford F150 is the best selling car in the US by a long-shot and it's a gas guzzler. Given that, I don't think consumers care a lot about how much they pay in taxes when deciding on a vehicle to purchase.

I don't think this'd have the incentive that you're suggesting it would unless something else is done, such as increasing the tax overall.