jvermillard

I use it everyday and the $20 plan is fine

I use it mainly for embedded programming and I find codex way better than claude. I don't my the delay anyway I'm slower to code carefully crafted C

I'm using Debian mainly for the last 20 years. I switched my laptop from Ubuntu to Fedora, mainly because Ubuntu snap madness and Debian was not working well on my framework 12gen. I was a bit skeptical due to previous experiences with redhat/fedora, but fedora was solid for the last 6 months. I'm thinking about migrating my desktop from Debian to Fedora.

I did the full interview process (11?) it didn't worth the time spent

same experience with Amazon a while ago, same with Microsoft, looks like ghosting is common

Apple hardware which can be destroyed by software, the M1 speakers: https://github.com/AsahiLinux/docs/wiki/Feature-Support#spea...

A good intro to tamago: https://media.ccc.de/v/36c3-10597-tamago_-_bare_metal_go_fra...

I already package some of the toolchain I use in containers because vendors tends to depends on old version of libc or curl and never update..

After watching https://www.youtube.com/watch?v=-enIM4x-KPA I I want to add it to my toolchain containers and have everything in one place.

I wonder how it will be priced by GH or using alternatives like: https://github.com/cdr/code-server

But since most of C developers are now using vscode if the performance are fine this could change the way embedded software development tools are distributed.

[Edit] the pricing is now public and looks fair:

Instance Type (Linux) Per-hour rate

Basic (2 cores, 4GB RAM, 32 GB SSD) $0.085

Standard (4 cores, 8 GB RAM, 32 GB SSD) $0.169

Premium (8 cores, 16 GB RAM, 32 GB SSD) $0.339

another cool one is the 70's one using the Concorde: https://motherboard.vice.com/en_us/article/8q8qwk/the-concor...

yes, but without communication security

Mirai is pretty basic and use default device password which wasn't changed by the end user, so manufacturer will probably says it's all user fault

I recently experienced a bug with OpenSSL 1.1 and the team was pretty reactive! I'm using OpenSSL 1.1 because it's the only DTLS implementation featuring all the extensions (OCSP stappling) and ciphersuites (AES-CCM-8) I need.

you can use coaxial cable if you are using it for testing or education. so you don't "pollute" the legit GSM communications.

I hope they will rewrite awscli with it. Today it's quite painful to run it on coreos (python/pip ran in a container)

Strange they dont mention AES-CCM at all. I'm using it a lot in IoT applications (dtls). It's not frequent in the "web" world?

~20fps on my nexus 9 (chrome)