2,024 karma · joined February 11, 2014
But to me it looks like you just want a laptop that does it's job reliably and have a limmited budget.
Also as, machinestops said, you can get the Framework laptop prebuilt.
What you mentioned in the first paragraph is not vaccination, it is called variolation. It predates vaccination by a large margin and was far more dangerous.
Proprietary platforms moderating user content on themselves is not an infringement of the users free speech rights. Proprietary platforms are not public spaces, they are private property and guests (users) have to abide by the house rules or be kicked out.
The simple explanation for that is that you, the user, are not the customer. A lot of software today simply does not need to cater to the needs of the user because the user has no choice in using the software or not. This is either because of network effects, monopolies, DRM or simply not having the decision power within a hierarchy. Even if software development practices are better than ever, the software developers are less aligned with software users than ever. It is an increasingly adversarial relationship.
It is not quality that has gone down, it is an alignment problem.
So why remain stuck importing CSVs into Excel when you can use Power Query to import Parquet. Why remain stuck using VBA in Excel when you can use Python in Excel.
I do not think an Excel user can be convinced to move to things like Jupyter, R, databases, etc. since they won't even make the jump to Access but maybe they can be convinced to use modern features of Excel.
(I expected Roman puns and was not disappointed)
They can not be refurbished or recycled into new blades but they can be repurposed to produce street furniture, reinforced plastic pellets or even as a concrete ingredient. So far there is not enough of an economic incentive to find uses for the quantity of blades being discarded instead of just dumping them. There are however companies and research projects working on making blades more recyclable and sustainable.
I also don't think dumping them is a huge issue. They do not leach toxic chemicals, do not produce microplastics, do not decompose into greenhouse gases. They are just a very voluminous waste product. In the transition towards a sustainable future I believe wind turbine blades are a really cheap technical debt to acquire.
Biggest aircraft really is a fuzzy thing.
What is big? The StratoLaunch, the Hughes H4 and the An-225 have a bigger wingspan. The Beluga Xl, the DreamLifter and the AN-225 have a bigger lift capacity.
What is an aircraft? As you mentioned airships and the Starship + Super Heavy both outclass it.
There is no shame in claiming longest plane or largest internal volume plane instead of biggest aircraft.
On my Lenovo laptop I have a toggle I can switch any time between battery saver mode(stay at 80%) and fast charging mode (charge asap to 100%).
If when designing products you never even let users choose to learn, you guarantee you will have a stupid user base. Stop endorsing stupidity.
I find that almost all layout algorithms for database diagrams are rather poor.
As long as you are doing OLTP using an RDBMS, I believe the proper way to "denormalize" is to just use materialized views and therefore sacrifice a bit of write performance in order to gain read performance. For the OLAP scenario you are ingesting data from the OLTP which is normalized therefore it's materialized views with extra steps.
If you are forced to use a document database you have to denormalise because joining is hard.
So if by scale you mean using a document database, sure, but otherwise, especially on SSDs, RDBMSs usually benefit from normalization, by having less data to read, especially if old features (by today's standards) like join elimination are implemented. Normalization also enables vertical partitioning.
There was an argument to be had about RDBMSs on HDDs because HDDs heavily favour sequential reads rather than random reads. But that was really the consequence of the RDBMS being a leaky abstraction over the hardware.
Document databases have a better scalability story but not because of denormalization. Instead it's usually because of sacrificing ACID guarantees, choosing Availability and Lower Latency over Consistency from the CAP (PACELC) theorem.