close2
The tools just work and I got used to the language really quickly.
I did hate that it was bytecode. It just felt wrong to run bytecode on an ESP32. OTOH it just works, and I have never noticed any performance problems.
My latest project is a controller for a slave-clock: https://gitlab.com/close2/nebenuhr-toit (There is also a Garmin repository that allows me to control the clock using my Garmin watch.)
Disclaimer: I had to use toit (floitsch is my brother), but it really is a nice language and development environment.
[Edit: typos..]
Here are 2 quotes, which give you a pretty good idea about the whole article:
> They’re spending minimum $2K to vibe code a Photoshop competitor when Affinity Photo is free and Photoshop costs $200 a year. Not very smart economics.
and
> Instead of hurling hate speech and bile at thousands of software engineers who lead innovation at large companies (Adobe, Autodesk, Maxxon, Celsys, and others), show them some gratitude for their efforts. They are the engineers who innovate and everyone else follows.
Ask HN: What are your favorite tips/tricks about IDEs that aren't well known?
I'm preparing a presentation to help my coworkers make better use of the tools we all use and would be interested in what other devs recommend.My presentation is focused on windows, IntelliJ,... (What we use at work) but any tip is welcome.I currently have:IntelliJ Shortcuts: Shift-F6, Ctrl-Ctrl-arrow, Ctrl-Shift-C/V, Ctrl-E, Ctrl-Shift-arrow, Ctrl-Shift-F Functionality: Shift-Breakpoint...
An even earlier version used an atmega and was powered from batteries [3]
Those slave-clocks are pretty loud. Both versions have a way to pause the clock.
https://gitlab.com/close2/nebenuhr https://gitlab.com/close2/nebenuhr_hardware https://github.com/close2/nebenuhr