My Sony doesn’t have this length limit, but will readily overheat and turn off after several minutes of highest-bitrate recording. So no, overheating is trivially protected against via temperature sensors, not some arbitrary timeout.
Auto is an improvement for C++ only because of its uniquely unergonomic type system and standard library. I'd very much prefer writing something like `iterator<auto>` instead of `auto` or `std::map<lotsofchars>::iterator` and not be told by every linter to change most explicit type declarations to `auto`.
Bambu and Fusion360 sure look nice, but if you're on tighter budget, 3D printers became both cheaper and more reliable in general, and FreeCAD recently got to 1.0 and is quite capable.
I worked alongside people using early versions of Makerbot and Ultimaker, and those were a maintenance nightmare. But recently I got a Kobra 2 Pro for $200, and it's both more capable and easier to use than those old monsters. With PLA it's pretty much hassle-free, no need to tweak anything except print orientation and maybe some support options.
Well it doesn’t need to be visible to work in contrast to camera. Seriously though, no technological and almost no economic barrier preventing embedding a mic into every wireless communication chip.
Absolutely. The main problem with python typing is that checking types is optional. A dialect with mandatory types (with inference) and runtime/load-time checking would be great.
If it’s 100x better than no types, then probably 10x better than C++ type system. It takes some time to unlearn using dicts everywhere, but then namedtuples become your best friend and noticeably improve maintainability. Probably the only place where python type system feels inadequate is describing json-like data near the point of its (de)serialization.
Congratulations, looks like a big upgrade! Haven't had the opportunity to test it much yet, but I already see how the new measurement tool is much more useful. It was really annoying in previous versions, to have a 3D model of something but no convenient way to measure it.
Very nice, I'd use it as one of the starting points if I was to learn 3D graphics as it touches upon a lot of math details in a seemingly simple problem.
Some Panasonic inverter microwaves don't suck. I have Panasonic NN-DS596M and its both featureful (almost a proper oven) and simple to control if you don't try to use every mode.
Peer reviews are very surface-level, often delegated to inexperienced students, and not incentivized well to do any deep analysis except checking for proper references (the incentive here being making the author cite you or your friends). Been that student.
I myself started programming with Delphi from 90s, but your arguments sound like only a perfect toolkit would be useful. I'd be perfectly happy to have 80% of Delphi 7 VCL in web-native format with a clear defined way to add custom components that fit in. Like color picker, which more often than not needs customization. And not like it was themable back then. WinXP-level theming should be enough.
Bootstrap started as something like this, but it both evolved too quickly IMO, and for some reason a generic look on the web is considered bad (by who? marketing? designers? even users as they think lack of distinctive style means lack of developer skills?)
Angle grinders are just awful in their versatility. It’s almost always a wrong tool for the job, but the right specialized tool often costs more or not readily available.
Valid points, though for safety I thought less about shock and more about fire: the DC arc is much more stable, thus the switches, breakers and relays have to be more robust. The rated DC voltage of magnetic relays is about 1/10 of AC.
I'm not a pro in these systems (yet, I hope), but my understanding is that, beside lack of demand, HVDC is a safety nightmare compared to AC, and inverters are getting more efficient each year. So, even given the choice, I'd keep AC home-wide distribution and set up inverters in key places, with exactly the highest required voltage.
This comment might finally push me to try DuckDB, thanks. I’m quite proficient with scientific python in general, but Pandas API is just alien (and slow). SQL is more natural for its domain.
For some reason many people don’t get such abbreviations: I’ve created an internal library ‘i8r = imagesaver’, explained this abbreviation everywhere, and some 5 years later, as we are transitioning off of it, about 10% of users don’t call it i-eight-r.
Thanks for the great overview! This is why I'll never want to deal with HVDC: all this, with increased risk of arcing, and "conventional" electric shock, no thanks
C++ on linux is indeed pleasant if you use only distro-provided library versions. Some specialized library with specific version, also no big deal. Need some upgraded version of a widely-used library -- get containerized or prepare for real pain.
As a (non-web) developer, I just don't trust PWAs: I assume they'll break their offline functionality in the most unfortunate moment while being not as tightly integrated into desktop as proper apps (even those using Electron). So I just keep using website as that has a more clear mental model.
You probably don't need full text search, but only exact match search and very efficient time-based retrieval of contiguous log fragments. As an engineer spending quite a lot of time debugging and reading logs, our Opensearch has been almost useless for me (and a nightmare for our ops folks), since it can miss searches on terms like filenames and OSD UX is slow and generally unpleasant. I'd rather have a 100MB of text logs downloaded locally.
Please enlighten me, what are use cases for real full-text search (with fuzzy matching, linguistic normalization etc.) in logs and similar machine-generated transactional data? I understand its use for dealing with human-written texts, but these are rarely in TB range, unless you are indexing the Web or logs of some large-scale communication platform.
I know about LastPass, but how infamous is TeamViewer? for me it's like Zoom, ugly and clunky, but still somehow more reliable and featureful than competition.
Sorry, cannot answer these questions competently. From my understanding, LG has monopoly on TV-scale OLED displays, so others big players in premium TV market (Sony and Samsung come to mind) bet on productizing uLED.
Any data block that must be fully received before processing comes to mind (e.g. websites’ html), just request retransmission of parts that didn’t make it in first pass. Funnily enough it’s (realtime) video and audio that already uses UDP due to preferring timely data to complete data.
On the contrary, for me it’s hard to imagine video game with missed packets as the state can get out of sync too easily, you’ll need eventual consistency via retransmission or some clever data structures (I know least about this domain though)
microLED is the next plasma, with tiny non-organic LEDs. Organic LEDs have some problems with color gamut and (AFAIR) response time that make them inferior to plasma, whereas microLED, while still exotic, is being rapidly developed.
I've even worked on a color science-related project that attempted to use LG OLED TV as a poor man's reference display, and turns out they use a lot of tricks like dithering, heavy power limiting and low brightness resolution for each subpixel that make them look bad when pixel-peeping.