HN user

awjlogan

172 karma
Posts4
Comments74
View on HN

I was addressing your statement that Earth is always changing. Yes, of course it is, obviously at +/- 20°C little that we recognise now would survive, but the transition is a lot less painful for you and yours if it happens over millions of years rather than a few centuries.

The one hope is that renewables and batteries continue to reduce in cost, and grids everywhere develop around that paradigm. Economically, it’s inevitable, but there’s a lot of (to be stranded) money, social, and political will against it.

I'm don't think it's ridiculous - it's simply a positive acknowledgement you've seen the message, even if there's no action required. The alternative would be repeated reminders until some timeout. I would imagine that timeout might come with an enforcement order, even if you have nothing to declare.

This is not the case here as the software is required to use the hardware they’re selling at any quantity. The software is cost entirely for them, if you’re not buying the hardware you’re not using the software. Given they support Linux for the paid version, its development is already paid for. Absolutely say you won’t provide support for free tier users. Today’s free tier users are tomorrow’s purchasing managers. FPGA is not a big market, so you have to capture comparatively few people for each unit of market share. Good silicon without good software is just very expensive sand.

No, you don't have to. If you are employed through a company, stay below £100K income and don't have other income then (generally) you don't need to do a tax return - it's all handled automatically through pay as you earn payroll. However, as shown, a lot of people are self employed, want to claim deductions, have some side income etc. However, for those that do need to, it is really straightforward.

N=2, but my Decathlon bikes have well over 50000 km between them with no issues, beyond the usual wear and tear. Value wise, they are fantastic. They are road bikes, however, not the folding specifically.

My feeling about programmable IOs is they’re fun, but not the right choice for commodity high speed interfaces like USB. You obviously can make them work, but they’re large compared to what you would need for a dedicated unit. The DVI over PIO is a good example: showed something interesting (and that’s great!) but not widely useful. Also, a lot of protocols, even slow ones, have failure and edge cases that would need to be covered. Not to mention the physical characteristics, like you’ve said for high speed USB.

I haven’t heard a peep about conscription, can you provide a source? There was some vague national service proposal for school leavers a couple of years ago, but that was it.

Maximum power output and maximum (assisted) speed are generally legislated. In the UK, an e-bike is up to 250 W and 25 kph. More than that, it would classify as a motorbike and you'd need a license (not particularly onerous). The bike itself is often built differently to accommodate the different power profile.

As a pedal cyclist, I feel that's a reasonably sensible limit as much faster than that you should be more experienced as a cyclist to control the bike and anticipate the conditions.

The Raspberry Pi SoCs optimised for cost rather than power consumption (or maximum performance). This is an engineering trade off, not a criticism. More power partitioning requires more area, more complexity in design and verification, and more expensive external components to support the internal voltage domains.

Another comment mentions the RP2xxx microcontrollers. If you look at those, they are optimised for compute power and data throughput rather than low power operation. I think it's a reasonable choice - the Pico boards are pretty sturdy and the original target is people running MicroPython, Arduino, etc rather than looking for µA standby currents.

This is a pretty standard document length. Modern microcontrollers have similar lengths (e.g. ATSAMD51 is ~2000 pages). Some of it is not software related, things like pin outs and electrical and mechanical descriptions.

It does take a huge amount of work to write and maintain. Typically the authors are not technical, so it also relies on the designers being available to answer questions as well. Then there’s a choice of how it’s written: narrative and potentially imprecise but readable, or terse and precise but hard to read. There’s both styles in the same document, terse for register descriptions.

The two big differences are 1) the rate of change (a huge amount higher than most planetary systems) and 2) that we have a large and growing population dependent on the many services our planet provides at a stable temperature. Of course, completely neglecting the rest of the natural world.

Much of the actual day to day work is. Typically graduate students, so they’ll be 22-26. That’s not a critique of their intelligence or potential. Students get progressively more experienced of course, but professors aren’t writing code most of the time.

A problem with academia in general is the lack of staff positions. Post docs finish their time then it’s either leave academia or become a professor. There’s few positions for those who want to just do research as a career, rather than pushing for a professorship. This means there isn’t a stable and experienced core of people.