Gas-powered cars are indeed much cleaner, they are very popular in Armenia because of favorable pricing compared to petrol. And while air in cities here may not be very clean, it's generally not because of cars: people burn trash in winter and there are a lot of dust in the summer.
Thankfully many new cars are Chinese EVs and most people are installing solar panels, and it doesn't seem to be environmentally driven at all, just economics.
Natural gas heating is not the problem in this case, it burns very cleanly with semi-modern heaters. The pollution is from coal, wood, and especially all kinds of trash (plastic, painted cardboard, pieces of various engineering wood products).
Do you have a recommendation for an inexpensive one? I’ve worked with OceanOptics Flame series, but they’re not exactly cheap, and their software was crap.
There’s growing consensus that with uv python tooling finally became good enough in terms of both speed and functionality, no need to choose one or the other (like, poetry had functionality but was extra slow).
The bezel is kinda functional on these watches, also they need it for huge water resistance. This Pebble is more comparable to traditional dress watches which don't have a prominent bezel.
30m (3 bar) basically means splash-proof, not even your stated 1m (activity while submerged, I suppose). Like, 30m is IPX4-5, 50m is IPX6 (very rough equivalence), so 30m is the barest minimum expected from a watch.
They are both not easy to make great, but with TUI you have way more constraints than with GUI so you can make something decent quickly and focus on important interaction and not on pixel-perfect button alignment.
Windows 98-XP GUIs were the best for such cases: there were clear design guidelines, everybody used native components, and GUI designers in IDEs were practical.
Didn’t really study this aspect, but it feels like thick AAC blocks would be better for seismic stability than those tuff stone blocks popular in Armenia. It’s lighter, glues to neighboring blocks better due to perfect shape, and has better heat insulation.
It would be amazing if AAC-like material could be produced on-site economically to create a lighter form of monolithic reinforced concrete construction, like filling a formwork with expanding foam.
It really is amazing, you can build a whole 2-story house out of it quickly using polymer-based glue instead of mortar, only using traditional reinforced concrete in some critical places. Was quite popular in russia, last I checked. Unfortunately hard to find in some better CIS countries.
In general I agree, but too much resilience can lead to worse infrastructure. Where I live, a couple hours of unannounced electricity outage every week is a non-event, so wires are patched in more and more points. And there's little motivation to invest significant money and time once to replace them by something more robust.
Probably the one type of PHEV that should survive is basically a BEV with builtin backup generator. One that's not necessarily powerful enough to drive you directly at full speed, but enough to basically eliminate range limitation of a (cheaper and smaller) battery by continuously charging it when needed. Maybe this 'backup generator' can even be made as a removable option.
I'm thinking of a semi-rural use case, when your typical daily trip is 20-50 km, but the charging infrastructure is poor and occasionally you do need to drive 200-300 km in winter.
There are now quite a few options for wifi APs with cellular backup. I use TP-Link, and it's ok for the price, I guess, and supports adding OneMesh range extenders.
The problem with this setup for me is that it doesn't work with uplink that sometimes becomes unstable yet nominally working, and in general LTE fallback triggers slowly.
Are there any prosumer-friendly options for connection bundling, which can balance uplinks continuously?
Probably has more to do with responsibility outsourcing: if SaaS has security breach AND they tell in the contract that they’re secure, then you’re not responsible. Sure, there may be reputational damage for you, but it’s a gamble with good odds in most cases.
Storing lots of legal data doesn’t seem to be one of these cases though.
For me the most annoying would be a technically correct solution that completely ignores the “higher-level style” of the surrounding code, at the same time defending the chosen solution by referencing some “best practices” that are not really applicable there for some higher-level reasons, or by insignificant performance concerns. Incidentally, LLMs often produce similar problems, only one doesn’t need to politely argue with them.
Compressed jsonlines with strong schema seems to cover most cases where you aren't severely constrained by CPU or small message size (i.e., mostly embedded stuff).
There should be two dark modes: a simple dark mode, like most dark themes today, to work in dimmed lighting, and an actual night mode, designed to be legible but not mess with adaptation in total darkness. I don't know the research on this (and I'm sure military and aviation have lots of data here), but intuitively it should use mostly thin red and green lines.
Typical web image quality is like it is partly because of lack of support. It’s literally more difficult to show a static HDR photo than a whole video!
Mint/Cinnamon has been my favorite for at least 5 years, after an assortment of KDE/Gnome distros. Basically the only argument for me being on Mac now is full Adobe graphics software support. (I dislike their business practices as anybody, but Lightroom CC is genuinely good tech, and gets useful updates at least yearly).
This is probably due to most software working with graphics somewhere (GUI, printing), and font sizes and resolutions are predominantly imperial (pt/dpi).
A bit off-topic, but denoise in LR is like 3 years behind the purpose-built products like Topaz, so a bad example. They've added any ML-based denoise to it when, like a year ago?
from cursory reading of the article I don’t see that author’s problems are specifically with Grafana in its best use case (metrics), but with other products from Grafana company, for which are a lot of alternatives.
Grafana dashboards itself (paired with VictoriaMetrics and occasionally Clickhouse) is one of the most pleasant web apps IMO. Especially when you don’t try to push the constraints of its display model, which are sometimes annoying but understandable.
In abstract case, you'd probably want to use xy color coordinates from xyY color space to specify LED color. Or even wavelength + spread, as you've tried. Those were the models that were used in one microLED-related research project I was part of.
Using those in images however would be another can of worms, you'll need some kind of physics-based rendering with good HDR tone mapping, as the human perception of light-emitting object against reflective background is highly non-linear.
For your use case it would probably be better to develop a standardized testing setup and just take RGB or XYZ coordinates from an image taken with a calibrated camera. Something like this:
* "standard gray" material surface
* a hole for LED with some kind of light pipe of standard shape
* uniform diffuse lighting of intensity computed to be proportional to your LED power measured in a standard way.
In this way it should be possible to create a catalog of LEDs useful for designing products.
One of the problems seems to be that most moderately complex companies where any one system would be fine with Compose would want to unify their operations, thus going to a complex distributed system with k8s. And then either your unified IT/DevOps team is responsible for supporting all systems on k8s, or all individual dev teams have to be competent with k8s. Worst case, both.
For certain definition of realtime, certainly (as would any system with bounded ingestion latency), but it’s not low-latency streaming realtime. Tens of seconds or more can pass before new data becomes visible in queries in normal operation. There’s batching, there’s merging, and its overall architecture prioritizes throughput over latency.
Isn't the Online part here about getting results immediately after query, as opposed to overnight batch reports? So if you don't completely overwhelm DuckDB with writes, it still qualifies. The quality you're describing is something like "realtime analytics", and is a whole another category: Clickhouse doesn't qualify (batching updates, merging etc. — but it's clearly OLAP), Druid does.
I wouldn’t be surprised if many construction sites have no way to get reliable internet connection without adding complex infrastructure: think of an underground parking with poor cellular coverage even on surface (in a country without Starlink support for extra difficulty).