floatboth

10 ms·

181.
by floatboth 5y ago
Also Bazel is very "corporate", it's not designed for projects that want to be good FOSS unix citizens. Very telling: "common c++ use cases" https://docs.bazel.build/versions/4.2.2/cpp-use-
182.
by floatboth 5y ago
Just like tup, redo keeps popping up as a nice conceptual thing, but none of these take off in practice. For most projects the winning build system is not the most conceptually interesting one, nor the most flexible one. It's the most
183.
by floatboth 5y ago
No, Sway supports downscaling. Augmenting downscaling with exact fractional scales is still in discussion: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/i... (And Firefox has a prototype implemen
184.
by floatboth 5y ago
Directly using physical PPI has basically never taken off anywhere. Everyone is using "arbitrary 1x" because designers and developers have never started using physical dimensions for digital UI elements. Most people speak in &quot
185.
by floatboth 5y ago
In a "logical pixel" system (macOS, Wayland, …Android??) the scale is the relationship between logical and physical pixels. In an "app go draw bigger stuff" system like Windows, it's just the factor of how much bigg
186.
by floatboth 5y ago
Oh it does? Nice. Kinda expected Apple to go full asshole mode on that.
187.
by floatboth 5y ago
But only when they make a glossy one: https://www.youtube.com/watch?v=3mTV1TOblbA
188.
by floatboth 5y ago
That's double the PPI compared to 27" 1080p ;) Granted, the usual "non-retina" 27-inch resolution was 1440p, but it's still a monitor you could use 2x scaling on. Yeah 1.75x or even 1.5x would be kinda preferable if
189.
by floatboth 5y ago
Yep, trying to find PPI based rules of thumb is silly. The better definition of "retina" is far simpler: you render UI at >1x scale on it.
190.
by floatboth 5y ago
It's really stupid to force Thunderbolt usage though when USB-C has an alt mode for DP directly.
191.
by floatboth 5y ago
I'm using a 28" 4K (with Wayland, which does scaling exactly like macOS) — used to use 1.5x with downscaling but switched to 2x "huge UI" for perfect crispness and honestly? It's not bad. It's actually good. Do
192.
by floatboth 5y ago
ehh… It is pretty easy to use but there's way too much bundled stuff in there, you're always under FreeRTOS, and Wi-Fi support is all proprietary blobs (but that's unfortunately the case with every embedded Wi-Fi chip… unlike
193.
by floatboth 5y ago
nRF52s are definitely not extremely cheap, they're high-quality fully-documented dev-friendly chips with lots of onboard resources. If you want cheapest BLE, there's some utter crap from Dialog Semiconductor that comes with a
194.
by floatboth 5y ago
You also do not have to use their tools. Use Rust with nrf-rs, or Apache Mynewt (with a fully open source BLE stack), or libopencm3, or…
195.
by floatboth 5y ago
Yes, the 51 is really old by now. The 52 line extends down as far as the tiny nRF52805. The 51822 is not nearly as fun to work with as the 52s, e.g. current Apache Mynewt with NimBLE doesn't even fit into the 51's tiny flash, the
196.
by floatboth 5y ago
A big design goal of Protobuf was long-term evolvability of message definitions with backward and forward compatibility. How rich is ASN.1 in that aspect?
197.
by floatboth 5y ago
No, not in a capability-based environment. Once you cap_enter() on FreeBSD, you can't – that's the whole point. Same in proper WASI runtime implementations. Please don't assume people are stupid ;) These sandboxes have been c
198.
by floatboth 5y ago
Ideally they should be turned into open source projects. Google's https://abseil.io and Facebook's https://github.com/facebook/folly come to mind.
199.
by floatboth 5y ago
But conveniently the at() stuff has allowed for capabilities-based security with Capsicum, CloudABI (RIP) and now WASI. Since the at() functions exist, these environments can just not have a global filesystem namespace – there is no open(
200.
by floatboth 5y ago
I wouldn't want an IDE to ever warp my fucking mouse pointer!
201.
by floatboth 5y ago
Meanwhile I'm carefully importing KiCad symbols and footprints (and polishing them and contributing to the community library) into a much less popular, newer open source EDA tool… because it's just that good: https://
202.
by floatboth 5y ago
You might not notice if you… don't ever scroll anything, I guess?
203.
by floatboth 5y ago
> particularly a compositor impl to go along with it Well, there is a wlroots impl, so I've just added a couple lines to wlroots to invoke this support from an env variable without having to modify the actual compositor :D https:&#
204.
by floatboth 5y ago
> the whole system is incapable of providing such feature in pluggable way No, the system is perfectly capable, it's just hard to get all compositor authors to agree on a common protocol (and to agree that it's necessary in the
205.
by floatboth 5y ago
There are SPI headers for flashing on many many desktop mainboards.
206.
by floatboth 5y ago
Vendor-provided SDKs are typically not good. Nordic's is one of the more decent ones and it still has a messy makefile based build system that's horrible to use. With nrf-rs you just use it as a cargo dependency. You don't ha
207.
by floatboth 5y ago
I'm not sure if/how this is improved in KiCad 6 but from the KiCad 5 tutorials I've seen, "manually match symbols to footprints" was its approach to library management :/ I'm learning PCB design with http
208.
by floatboth 5y ago
Yes, but "whether" is kinda weird here. The first (community development) requires the second (open sorce). If upstream can accept your contributions, this means you've already forked it for yourself.
209.
by floatboth 5y ago
HTC actually made a phone with real sapphire glass..
210.
by floatboth 5y ago
Video decode acceleration is very nice for battery life and freeing up the CPU for that LLVM build you're running in the background, but it's absolutely not a requirement, it's nowhere near as important as GPU rendering. Heck

More ›