Meh. If you have the resources, buy whatever makes you happy.
If a bigger house makes you happy because you have space for your hobbies and you don't need to fight with your family members for space, buy a bigger house.
The whole "money doesn't bring happiness" thing is bullshit unless you are a Buddha.
A mansion in Malibu isn't going to make me happy, because I wouldn't know what the hell to do in Malibu. An upgrade from a 2-bedroom to a 4-bedroom home with a garage so I don't have to smell laser cutter fumes anymore and hack a ventilation system out a bedroom window? That very well might.
> An upgrade from a 2-bedroom to a 4-bedroom home with a garage so I don't have to smell laser cutter fumes anymore and hack a ventilation system out a bedroom window? That very well might.
As someone who upgraded from a 2 bedroom flat to a 3 bedroom house with a garage, I concur. Having a place to store my bikes and other “dirty” tools that’s not inside was such an improvement to my quality of life that I tell people to always look for a half decent garage when they buy. Especially if they also like cycling!
> She has agreed to a 10-year ban from holding executive roles in public or crypto companies.
So you can hold an executive role in a wholly owned private subsidiary of a public company, or hold a role in a Cayman Island company instead of a US company and have the Cayman entity buy the US entity. Rules like this don't actually do anything.
The ocean has already absorbed 30% of the CO2 humanity has emitted. It causes issues: ocean acidity rises, which reduces plankton ability to grow. Plankton being the base of the ocean food chain, all ocean life gets impacted.
You'd need to find a way to sequester carbon without it leaching in the water.
Random idea: What if we just sequestered it into elemental carbon pellets and let it sink to the bottom of the ocean? It should not react with the water.
One idea is to charcoal the wood, it makes it harder to decompose and is similar to pure carbon. I'm not sure if it's better to send it to the bottom of the ocean or just to a big hole on land.
People seem to have the assumption that OpenAI and Anthropic dying would be synonymous with AI dying, and that's not the case. OpenAI and Anthropic spent a lot of capital on important research, and if the shareholders and equity markets cannot learn to value and respect that and instead let these companies die, new companies will be formed with the same tech, possibly by the same general group of people, thrive, and conveniently leave out the said shareholders.
Google was built on the shoulders of a lot of infrastructure tech developed by former search engine giants. Unfortunately the equity markets decided to devalue those giants instead of applaud them for their contributions to society.
You weren’t around pre Google were you? The only thing Google learned from other search engines is what not to do - like rank based on the number of times a keyword appeared and not to use expensive bespoked servers
Ranking was Google's 5% contribution to it. They stood on the shoulders of people who invented physical server and datacenter infrastructure, Unix/Linux, file systems, databases, error correction, distributed computing, the entire internet infrastructure, modern Ethernet, all kinds of stuff.
Eh ... I question that 5% ranking is google's only contribution, even if it was important.
Everyone stood on the shoulders of file systems and databases, ethernet (and firewalls and netscreens, ...) Well, maybe a few stood on the shoulder of PHP.
Google did in fact pretty much figure out how to scale large number of servers (their racking, datacenters, clustering, global file systems etc) before most others did. I believe it was their ability to run the search engine cheap enough that enabled them to grow while largely retaining profitability early on.
More specifically on that last point, I remember reading something like Google's biggest contribution hardware-wise was using lots of cheap, easliy-replaced distributed storage with redundancy instead of expensive large singular storage with error-correction? Or maybe it was memory and not storage. Whatever it was I remember them not caring as much about error correction as others, and being able to use relatively cheap hardware because of it.
Isn't it really the other way around? Not to say OpenAI and Anthropic haven't done important work, but the genesis of this entire market was paper on attention that came out of Google. We have the private messages inside OpenAI saying they needed to get to market ASAP or Google would kill them.
The thing I dislike about monorepos is that people don't ship stuff. Multiple versions of numpy and torch exist within the codebase, mitigated by bazel or some other build tool, instead of building binaries and deb packages and shipping actual products with well-documented APIs so that one team never needs to actually touch another team's code to get stuff done.
The people who say polyrepos cause breakage aren't doing it right. When you depend across repos in a polyrepo setup, you should depend on specific versions of things across repos, not the git head. Also, ideally, depend on properly installed binaries, not sources.
That makes sense when you depend on a shared library. However, if service A depends on endpoint x in service B, then you still have to work out synchronized deployments (or have developers handle this by making multiple separate deployments).
To be fair, this problem is not solved at all by monorepos. Basically, only careful use of gRPC (and similar technology) can help solve this… and it doesn’t really solve for application layer semantics, merely wire protocol compatibility. I’m not aware of any general comprehensive and easy solution.
> However, if service A depends on endpoint x in service B, then you still have to work out synchronized deployments (or have developers handle this by making multiple separate deployments).
In a polyrepo environment, either:
- B updates their endpoint in a backward compatible fashion, making sure older stuff still works
OR
- B releases a new version of their API at /api/2.0 but keeps /api/1.0 active and working until nothing depends on it anymore, releasing deprecation messages to devs of anyone depending on 1.0
I always thought of Docker as a "fuck it" solution. It's the epitomy of giving up. Instead of some department at a company releasing a libinference.so.3 and a libinference-3.0.0.x86_64.deb they ship some docker image that does inference and call it a microservice. They write that they launched, get a positive performance review, get promoted, and the Docker containers continue to multiply.
Python package management is a disaster. There should be ways of having multiple versions of a package coexist in /usr/lib/python, nicely organized by package name and version number, and import the exact version your script wants, without containerizing everything.
Electron applications are the other type of "fuck it" solution. There should be ways of writing good-looking native apps in JavaScript without actually embedding a full browser. JavaScript is actually a nice language to write front-ends in.
> Python package management is a disaster. There should be ways of having multiple versions of a package coexist in /usr/lib/python, nicely organized by package name and version number, and import the exact version your script wants, without containerizing everything.
Well sure, every language has some band-aid. The real solution should have been Python itself supporting:
import torch==2.9.1
Instead of a bunch of other useless crap additions to the language, this should have been a priority, along with the ability for multiple versions to coexist in PYTHON_PATH.
There is a vast amount of complexity involved in rolling things from scratch today in this fractured ecosystem and providing the same experience for everyone.
Sometimes, the reduction of development friction is the only reason a product ends up in your hands.
I say this as someone whose professional toolkit includes Docker, Python and Electron; Not necessarily tools of choice, but I'm one guy trying to build a lot of things and life is short. This is not a free lunch and the optimizer within me screams out whenever performance is left on the table, but everything is a tradeoff. And I'm always looking for better tools, and keep my eyes on projects such as Tauri.
I think there's merit to your criticisms of the way docker is used, but it also seems like it provides substantial benefits for application developers. They don't need to beg OS maintainers to update the package, and they don't need to maintain builds for different (OS, version) targets any more.
They can just say "here's the source code, here's a container where it works, the rest is the OS maintainer's job, and if Debian users running 10 year old software bug me I'm just gonna tell them to use the container"
Yeah I'm not against Docker in its entirety. I think it is good for development purposes to emulate multiple different environments and test things inside them, just not as a way to ship stuff.
Agree on all fronts. The advent of Dockerfiles as a poor mans packaging system and the per-language package managers has set the industry back several years in some areas IMHO.
Python has what, half a dozen mostly incompatible package managers? Node? Ruby? All because they're too lazy, inexperienced or stubborn to write or automate RPM spec files, and/or Debian rules files.
To be fair, the UNIX wars probably inspired this in the first place - outside of SVR4 deriviatives, most commercial UNIX systems (HP-UX, AIX, Tru64) had their own packaging format. Even the gratis BSD systems all have their own variants of the same packaging system. This was the one thing that AT&T and Sun Solaris got right. Linux distros merely followed suit at the time - Redhat with RPM, Debian with DEB, and then Slackware and half a dozen other systems - thankfully we seem to have coalesced on RPM, DEB, Flatpak, Snap, Appimage etc... but yeah that's before you get to the language specific package management. It's a right mess, carried over from 90's UNIX "NIH" syndrome.
> correspondence set in Calibri looks like something dispatched from a leasing office
In general this is the way I feel about anything written in a Microsoft-, Apple-, or Ubuntu-supplied typeface. If you stick to system fonts you the pinnacle of embodiment of apathy in my book.
Have some backbone, browse through Google fonts, pick something that represents your organization and stick with it.
Even if you are a leasing office, pick a good font. That will make me more likely to lease from you because your attention to typography conveys to me that you will also be attentive to details in building maintainence. If you communicate in Times New Roman and Arial it tells me that you probably are apathetic about mold in the walls and electrical code as well.
While I appreciate nice typography like not many do (I decide on what editions of a book — especially classics — to get based on the typography and overall layout), I also appreciate that I may be easily swayed by good typography and land on a crappy outcome (I have several very lousy books that were done really well typographically :)).
So I'd never use that as a metric: yes, I care about typography, and if the content of the message is equivalent, I'll pick the one done better. But I do not expect everyone else to put as much weight on it.
If it's legible, the terms of a lease are way more important than the typeface. Anyone wasting time on the typeface of the contract would worry me more than comfort me with regard to knowing what's important.
Due diligence is a joke in the first place, nobody actually does anything these days beyond flip through some Powerpoints. They think their hockey stick graphs are some diligence but in reality every graph is engineered to be a hockey stick.
The vast majority of whether a deal is good or bad has nothing to do with anything you could be duly diligent about. It has everything do with whether the founders are clever executors to capture market, and the luck of the company in the coming years, the latter you cannot predict.
If a bigger house makes you happy because you have space for your hobbies and you don't need to fight with your family members for space, buy a bigger house.
The whole "money doesn't bring happiness" thing is bullshit unless you are a Buddha.
A mansion in Malibu isn't going to make me happy, because I wouldn't know what the hell to do in Malibu. An upgrade from a 2-bedroom to a 4-bedroom home with a garage so I don't have to smell laser cutter fumes anymore and hack a ventilation system out a bedroom window? That very well might.
reply