inkyoto

67 ms·

601.
by inkyoto 4y ago
… which is another testament to the fact that a wide memory bus is an attribute of server or hi-end components rather than «laptop parts» that one can throw into a bucket, stir vigorously, cook on a slow fire and get a M1 Ultra with a 1024-
602.
by inkyoto 4y ago
> So exceptions […] completely free when not thrown unlike return values. In C++, they are not. Since C++ allows objects to be created on the stack within the each current scope, every constructor call for such a new object has to regist
603.
by inkyoto 4y ago
> There is no cost to exceptions that are not thrown. Oh yes, there is. C++ compiler has to emit unwind tables, register destructors for RAII resources and generate the RTTI information (where applicable). In this trivial example, consid
604.
by inkyoto 4y ago
> […] and the insides are now laptop parts. The Mac Studio is simply the desktop computer that gets the Macbook Pro chips. «Laptop parts» connect M1 CPU clusters to RAM via a 512-bit wide (M1 Max) and a 1024-bit wide (M1 Ultra) memory
605.
by inkyoto 4y ago
> Contamination risk is a real showstopper for Mars, one of those problems that gets worse the more carefully you look at it. Not just Mars but anywhere humans choose to go to. Since a) discovery of extremophiles; b) humans themselves ar
606.
by inkyoto 4y ago
> How many businesses are so constrained by link times on Mac […] Long link times are not specific to OS X / iOS. Large C++ codebases are some of the worst offenders and emit obscene numbers of relocations and DWARF symbols (or simi
607.
by inkyoto 4y ago
You are barking up the wrong tree. The ABI compatibility is never expected nor is taken for granted, for it is an internal implementation aspect of an operating system. An ISA does not equate to an ABI either. Blaming Apple for devising or
608.
by inkyoto 4y ago
Yes, they do, and I can't think of an operating system (other than OS/400) where a module is not a single file or a collection of files. Could you please reference an implementation where it is done otherwise? The module system is
609.
by inkyoto 4y ago
> […] and excessive rebuilds are OK. Where does the presupposition of just some build tools, but not the others (if I am reading it correctly), resulting in excessive rebuilds come from? Apart from building a dependencies DAG for a pro
610.
by inkyoto 4y ago
I have 0 expertise in phone battery replacements, but I have one recent experience of a neighbour in my apartment building recharging his electric scooter, and a dodgy (or cheap or both) battery in the said scooter blowing up at 3am in the
611.
by inkyoto 4y ago
You have to be a little bit more specific than that and quantify and itemise the «many» part. Otherwise it is pure speculations, generalisations, arm chair theories and hand waving. What is a «vanilla system»? A brand new laptop? Then the h
612.
by inkyoto 4y ago
> The worst part is that […] The actual worst part is that it is impossible to draw a meaningful conclusion from a problem report like this one: > Mine also shines from the holes when closed. M1 Air. Noticed happens when browser is o
613.
by inkyoto 4y ago
Moreover, different languages implement the exception handling differently. The article focuses on C++, which has a notion of object destructors (most – but not all – programming languages don't have the destructors). Implications for
614.
by inkyoto 4y ago
> […] The market for peripherals and the like wasn't exactly open and there were all sorts of weird servicing deals. With beige boxes we didn't even need a formal procurement process for peripherals like keyboards and the like
615.
by inkyoto 4y ago
The same old story: the rise of «worse is better». UNIX workstations hardware was always miles and miles better[0], although it could no longer compete with the commodity PC hardware due to being exorbitantly priced. Coupled with highly agg
616.
by inkyoto 4y ago
Per-resource IAM policy generation alone is not even half good enough. Most AWS services have complex IAM policy requirements that are unique to a specific AWS service or product, and within each there is typically a subset of policies bein
617.
by inkyoto 4y ago
> […] and let them learn the language on-the-job so they can do low-priority legacy maintenance. And that is a problem frequently faced with fresh graduates and young developers (no disrespect to them) whose common reaction to legacy pro
618.
by inkyoto 4y ago
> And COBOL is still carrying the economy. Not by choice but rather out of desperation and necessity to continue to run the mission critical code, mostly in banking, finance, and it is also occasionally encountered in government services
619.
by inkyoto 4y ago
> My main gripe is the idea that MERGE is somehow better than INSERT ON CONFLICT for upserts […] I, for one, find the MERGE syntax to be easier to read, more flexible and versatile and, most importantly, standardised. It is, effectively,
620.
by inkyoto 4y ago
I have suggested MERGE as the last resort (due to the the main table having 40(!) circa columns), not as the preferred option – please refer to the last paragraph in my comment. Yes, it is difficult indeed to recommend something more specif
621.
by inkyoto 4y ago
> Maybe we can go so far as to "Excuse me, if you wouldn't mind could you please write a short blurb on .... " You forgot to throw in an apology for an interruption: «Excuse me for an interruption, when you get a chance to
622.
by inkyoto 4y ago
It sounds like you are dealing with a denormalised data model. Relational databases do not handle the denormalised data models well, and 50 million records is a small dataset. Consider remodelling the data model and going up to 3NF [0], or
623.
by inkyoto 4y ago
Tooling has nothing to do with the schema evolution, normalised forms (4NF, 5NF, …) do. The trouble is that almost no-one does that. Relying on the tooling alone is either a self-delusion or the lack of experience. Usually both.
624.
by inkyoto 4y ago
> […] nobody used any […] With all due respect I don't know what to make out of absolutist, generalised statements such as this one.
625.
by inkyoto 4y ago
> It adds complexity to a narrow use case. It also simplifies the unnecessary complexity in many cases, and I have witnessed both. Just like one should not use an expensive Zeiss microscope to hammer nails into a concrete wall as a hamme
626.
by inkyoto 4y ago
> You can do all of this in the relational model […] That… depends. Right now I am dealing with the customer's 6NF relational model which I had up until now thought was purely theoretical and was not a naturally occurring phenomena
627.
by inkyoto 4y ago
Oh. Payments, wanks (and Megawanks) and CosmosDB – a unholy trinity, bless them all. I think I know what the Megawank was up to. Since Apple (not entirely sure about Google/Android) denies anyone direct access to the NFC hardware in an
628.
by inkyoto 4y ago
I don't understand where this comes from. If the problem warrants the use of a graph data model, property graph databases provide an efficient solution for that. Graph databases also excel at discovering distant relationships between l
629.
by inkyoto 4y ago
The UK style healthcare system is fundamentally flawed as it does not attempt to address the root cause of a health problem, and is skewed towards providing a tactical solution to the health problem instead. I.e. fixing up the patient just
630.
by inkyoto 4y ago
> […] switching between say Polish and English reading is a bit easier/faster mentally. How so? Specifically with Polish «szcz», «cz» and «ź» – for which English has no approximants; with the devilish «y» and with «ą» and «ę» causin

More ›