Recent submissions

Comment · 2 years ago
Thank you, this gcc14 option looks really interesting. With the lack of hardware of this class supporting RVV 1.0, this will be useful.
Comment · 2 years ago
While investigating the RISC-V ecosystem, we noticed that there isn't an easy way for developers to build and test their software on native hardware without buying it.

So we integrated custom RISC-V servers in our bare metal servers infrastructure and made them available to the public to enable the building, porting and testing of more native RISC-V software.

A 4 Cores TH1520 with 16 GiB of RAM and 128GB of eMMC is 15,99€/month.

Comment · 5 years ago
For reference, archivebox uses 250GB for 5000 links in my setup.
Comment · 7 years ago
Comment · 11 years ago
Comment · 11 years ago
I've migrated to Bittorent Sync: http://getsync.com it's a "no cloud" solution. They don't see your data.

I'm happy with it but I do have a NAS at home that serves as a "always on" sync point for my other devices.

Comment · 11 years ago
Comment · 11 years ago
From the article's footnotes:

> While on the subject of smartphone driven hardware, experience has shown me that software has a much shorter mean-time-to-obsolescence than hardware. Any gizmo that needs an app to make it work will have the service life of a bluebottle, as Apple’s planned obsolescence orphans the app with an iOS upgrade.

This has been my experience too and I wish manufacturers would remove the requirement on having an app to use/configure the device.

Because of that, I try to make sure that such devices I design provides a basic web interface that makes it possible to setup and use the device.

This is impossible or at least difficult if the device is powered by a 8-bit MCU but with the dropping prices of beefier MCU and linux-compatible SoC this shouldn't be an issue in the future.

Of course, there is also the issue of remote services that those devices often depends on, even if it's not exactly necessary sometimes.

Comment · 11 years ago
I'm using MQTT on my current project that involves interactive applications running on solar powered devices.

I'm using RabbitMQ for the broker, it supports MQTT too, this means I can use MQTT on the clients and the services on the backend only needs to understand AMQP.

I made a simple RPC system on top of it, unfortunately it's a homegrown solution as I couldn't use RabbitMQ RPC features with MQTT.

Comment · 11 years ago
Comment · 11 years ago
Comment · 11 years ago
My answer to some of those issues have been to use a folding bike and combining transport modes.

A 15km ride might be 13km of RER and 2km of biking, on some trips it's pretty damn fast even compared with a car that has to contend with traffic.

It doesn't solve the rain issue on the other hand. Especially as folding bikes generally have smaller wheels that tend to skid on wet pavement.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton