HN user

Arcsech

1,075 karma
Posts12
Comments206
View on HN

I don't disagree with your points about connected cars, but at least for CarPlay (I don't know about Android Auto), it's entirely an orthogonal concern. CarPlay is a standard for, basically, connecting an external display to your iPhone - it doesn't need to connect to anything other than the iPhone itself, and doesn't grant the car any access to the internet or anything, and IIRC the phone can't read anything meaningful from the car either.

EXACTLY. This lazy, backwards approach to tooling and workflow is why I jumped ship from logic design to software despite having an EE degree. VHDL/Verilog tooling is heinously terrible and everyone in the industry seems to be actively opposed to doing anything about it.

Oh yeah, that paragraph really nailed it. Every place I've worked that's started to go downhill, it always started with executives, who never acknowledged their role in the problem or did anything to fix it.

I'm increasingly convinced that a large portion of our problems as a society is our absolute refusal to hold anyone in power accountable for anything.

My concerns about toxicity on Twitter are less about what I want to see (I don’t use Twitter anymore myself, even), and more about the incitement to violence we’ve clearly seen is possible on the platform. Twitter should not be a platform for organizing a mob to invade the capitol and attempt to execute the Vice President, for example.

The author of that article is overly focused on the Linux (or similar) deployment model, which most definitely does not cover all uses of SQLite. The argument against 2) also depends on a feature available in specific versions of specific compilers, which again, a piece of software that supports as many use cases as SQLite can’t depend on.

Even in that model, I’ve long found that the arguments against 1) are weak in practice (especially with a well-designed and maintained lib like SQLite) versus the additional complexity added by depending on dynamically linked libraries.

Well, she went to a different doctor later who helped her diagnose & treat her allergies. Which made exercising easier too, turns out. Who’d have thought? (Her. One of the reasons she’d sought treatment is that the difficulty breathing through the nose was making it unpleasant to exercise.)

This is a great question! In my experience, the differences come down to:

- The doctor is going off a very short explanation you gave in a 30-minute appointment. If you have a serious medical problem, you can dump days, weeks, or months into finding information that matches your experience down to the fine details, which can very much matter - especially if you have an unusual case of something.

- There may be new information since your doctor was trained. Medicine has advanced a lot, and while doctors do their best to keep up, there’s more new research than any one person can digest.

- You will always believe yourself, never dismiss your experiences as “exaggerated” or “drug seeking”, and never blame your conditions on obviously unrelated causes.

That last one is especially relevant to people who aren’t cis white dudes. I’ve witnessed, with my own eyes, a woman talk to a doctor about chronic nasal congestion, and his response was to tell her to lose weight. Doctors habitually not believing the experiences of their patients has done incredible harm over the years.

That’s exactly why I used the phrase “source-available”, not “open source” - because those licenses aren’t recognized by the OSI. I’m actually of the opinion that if AGPL is open source, SSPL is too, no matter what some dorkwads as the OSI say. But I’m employed by a company that uses the SSPL, so I try to use the generally accepted phrasing to avoid being accused of “sowing confusion”.

Even if you’re worried about this, there are source-available licenses like SSPL or Elastic License v2 explicitly designed to prevent this, and which have seemingly been successful at doing so. The exact choice of license would depend on the kind of thing you’re worried about.

The shortcut to implementing this technique is buy a gaming console. Gaming companies seem very committed to their desire to root your box, so might as well just get one pre-rooted and use it for nothing else.

There are two parts to an inductive proof:

1. Assuming that a property is true for N, prove that it is true for N+1.

2. Prove that the property is true for some concrete N where the proof for step 1 holds.

The trick is that you need to be sure to pick your concrete N correctly, as the article demonstrates. In particular, the problem with the "solution" in the article is that the proof given for step 1 doesn't hold for N=1, because N+1=2, and then just follow the rest of the argument from the article.

I've been thinking along some similar lines myself recently, that I'd like to have notes that can link to code in some kind of semi-durable way (i.e. as resilient as possible to changes), be able to run code snippets in a variety of languages, etc., and the only things I've found that are able to do this are:

1) Emacs with Org Mode, which is very powerful but has a learning curve like a brick wall, even if you already know emacs. Also nearly impossible to use with anything except emacs (yes, there are mobile/web apps that understand standard org syntax... which doesn't help with any customizations you make, which is like half the point of org mode).

2) Glamorous Toolkit, which is based on Pharo Smalltalk and is easier to use than org mode, but less featureful, much newer (== smaller community, less support), and has many of same problems (i.e. can't easily use it on any non-desktop platform).

It's looking more and more like I'm going to have to build something myself for this.

I’ve poked around the code a bit - not thoroughly, so take this with a grain of salt - and it looks like it’s all Common Lisp. There’s a very thin JavaScript shim that applies commands from the server, but that’s pretty much the only non-CL thing.

That said, it presents as a “GUI”, but it’s really more similar to Blazor or LiveView than, say, Qt or even Electron.

What makes it "for devs"? I tried searching some programming queries that I'd typically make during a workday and the results were... fine, I guess, but it was basically just web results? Sometimes there were a few enhanced results, but they weren't very good or useful, like when I searched for `java string split` and got back enhanced results showing me how to split a string in Python and Javascript.

There's a bar of "search apps" along the bottom of the page that doesn't do anything if I click on any of them, so I dunno, maybe it would be better if I made an account and added some apps... or I could keep using DuckDuckGo and just type `!so java string split` when I forget trivial method signatures and want to search StackOverflow instead of figuring out what a "search app" is.

Also, this is really, really pushy about being your default search engine. That's a big step! It's like someone talking about moving in with you on the first date. Maybe convince me first?

I don't get it.

Cool. I don't feel like permanently dedicating a couple hundred megs of RAM to every site I need to use that decided to go chasing the latest counterproductive trend.

There are a few. But they're good for a vastly smaller range of use cases than they're applied to.

You're writing Google Docs? Good for you, you can use an SPA. You're writing a social networking site? That should be a regular HTML page, with a sprinkling of JS. Blog? HTML page. Issue tracker? HTML page.

Every site I've used that's been plain HTML and CSS, with maybe minor supplements in Javascript, is much nicer to use than any SPA. People claim they load faster, but I've never experienced that in practice - a plain HTML page loads in milliseconds, but downloading a giant gzip of Javascript and waiting for it to make a zillion API calls takes seconds.

GMail's HTML-only interface fully loads and renders in ~630ms for me. The SPA version takes 11.69 seconds.

lite.cnn.com loads in 287ms. CNN.com takes 4.25 seconds.

thin.npr.org loads in 112ms. NPR.org takes 1.47 seconds.

Need I go on? Even for the lightest one, NPR, if you assume loading an article on the SPA version is instantaneous, you'd need to load 14 articles to make up for the slowness of the initial SPA load. The others are all much worse. And this is with an adblocker enabled - this will only get worse with one disabled.

Using SPAs when they aren't strictly necessary is a great way to shoot your site's performance, usability, and accessibility in the foot. You can fix the usability and accessibility problems, but you need to devote substantial engineering resources to doing so, and those are free if you just use the damn plain HTML.

Racket has a surprisingly good cross-platform GUI library. I've been building a tool for streamlining some testing at work, and building in Racket makes it almost trivial for it to work across Mac/Win/Linux, even the GUI bits, and you get that Schemey goodness.