initplus

The obvious angle is AI contract generation. Docusign are uniquely positioned to build up a real training set of contracts.

Splitting assets between banks doesn’t change the insurance income collected by FDIC, and nor does it change the overall risk profile for FDIC - its artificial structuring behaviour. It’s a minimum, not a cap.

>however that solution only works because we have a non AI system to prove correctness

But this is actually a really common scenario. Checking a solution for correctness is often much easier than actually finding a correct solution in the first place.

GBTC is it's own weird separate thing, with a whole bunch of red flags. It's not yet an ETF. They don't even distribute the fund prospectus online, it's only available by email request.

Tracking for actual BTC futures ETF's is quite good. Arbitrary example: https://ycharts.com/companies/BITO/discount_or_premium_to_na...

GBTC has diverged so far because it doesn't have a public creation/redemption mechanism. Matt Levine briefly touched on this recently: https://www.bloomberg.com/opinion/articles/2024-01-04/put-th...

Trading in derivatives still affects the price of the underlying asset. Sellers of BTC futures contracts are hedged by holding BTC.

Bitcoin futures ETF's already exist - I'm not convinced that a spot price ETF is any huge breakthrough.

Bitcoin futures ETF's are already allowed - several exist and they track the BTC:USD rate relatively accurately. I'm not sure that a spot price ETF is really a huge breakthrough in terms of actual mechanics.

But approval is an opportunity to create hype and buzz around cryptocurrency.

RF is harmless below the point where it directly heats tissue.

Having a full strength cell tower transmitter inside your home is not safe due to the intensity of the transmission, it will directly heat tissue inside your body.

This would show the effect you want. Code like tests are likely to be very verbose, while often the actual vulnerability will come down to a handful of characters.

Delivering files is the easy part, integrating with the language tooling/buildsystem is the hard bit. Seemingly simple concepts like a dependency don’t translate neatly across languages.

Naive implementations of A* can break down in some common scenarios, with highly connected graphs where many solutions exist. Imagine a long barrier with the start and goal placed on either side at the exact midpoint.

Tie handling is really important! A* is often described as minimizing f(n), where f(n) = g(n) + h(n), g(n) = path distance so far, h(n) = distance to goal heuristic. But for any valid shortest path the remaining work for the algorithm to do is determined by the size of g(n). So when selecting the next node to explore you must minimize first by f(n), and then maximize g(n) as a tiebreaker. Same is achieved by breaking ties with LIFO.

Another TV related “don’t suck button: Nvidia defaulting to limited colorspace on HDMI outputs. Persists to this day.

iPhone Haptic Touch duration not set to “Fast” by default.

Nearly every attempt at starting a new aggregation site like hackernews or reddit has been a failure.

I’m not going to switch to a new website where no community exists just so I can pay for news articles. To work it needs to be integrated into an existing, successful aggregation website.

I would be "happier" to pay a subscription to an aggregation platforms like hackernews or reddit to access archived articles that are linked to these sites. In turn a proportion of that could be passed on to the underlying publishers that I actually visit. I have nearly zero interest in reading articles that aren't linked to from an aggregation site.

I don't want to read theguardian.com, or nytimes.com, or washingtonpost.com, or bloomberg.com, I want to read news.ycombinator.com. Paying an individual subscription to every possible underlying site that could be linked to from news.ycombinator.com is a non-starter.

vcpkg are forced to alter source packages because in the majority of cases upstream doesn't have working cross platform builds. They have weird broken CMakeLists.txt, incomplete compiler support, weird build incompatibilities with other libraries etc.

Unicode was originally designed with the dream of fitting everything into 16 bits. CJK unification was a controversial measure that enabled this, by combining "the same" characters together in Chinese, Japanese, and Korean. Microsoft (wchar), Sun (Java), Netscape (JS) and many others settled on a 16bit fixed width "Unicode" encoding (nowadays often labelled as UCS-2).

Later it turned out that 16 bits wasn't enough anyway, but we are left with the UCS-2 mess regardless. UCS-2 and CJK unification are historical mistakes in the development of Unicode that we are stuck dealing with.

Yeah - on the one hand I'm really happy for them. They are building something really cool, out in the open under the MIT license. Hopefully outside investment will help them accelerate their plans for Godot.

On the other, it's hard to see what the monetization pathway is here for the investors. I suppose plan to offer development consulting to firms using Godot? Some conflict always seems to come up with these "open source but commercial" entities.

I guess I still don't understand... how much customer service do you need to run a savings account? How do you even screw that up?

Operating a savings account like this one should be close to just picking money off the free money tree. It's wild to think that it costs them more to operate this than the margin they take off it.

"Unfortunately a lot of the graphics-related issues are indirectly caused by the game’s use of DOTS"

"The cause for unnecessary geometry is both the lack of simplified LOD variants for many of the game’s meshes, as well as the simplistic and seemingly untuned culling implementation. And the reason why the game has its own culling implementation instead of using Unity’s built in solution (which should at least in theory be much more advanced) is because Colossal Order had to implement quite a lot of the graphics side themselves because Unity’s integration between DOTS and HDRP is still very much a work in progress and arguably unsuitable for most actual games"

https://blog.paavo.me/cities-skylines-2-performance

Unity are spending too much money to develop far too little. New engine features are almost universally half baked (DOTS, UI mess). They acquire in demand features from the community just to let them wither (pro builder). The only thing that's consistent between different Unity features is how unpolished they seem.

Notably the mess they have made of DOTS seems to have been partially responsible for sinking Cities Skylines 2.

Just points to a mess at the leadership level. Their failed relicensing debacle shows the poor level of judgement of the C suite.

What is the underlying reason these consumer offerings have been such a failure? Something like a savings account should be the closest thing to free money there is - stick the cash into t bills, collect a margin on top and pass the rest back to the customer.

Do the marketing/cs costs really outweigh the margin? Or is it some issue with how the assets backing the account are invested?

Interesting to see that the worry could have been avoided if they had lined up their timelines better in the first place. If they'd compared the timestamp on the test readout to the last timestamp from the telemetry system, they'd have seen that the telemetry failed BEFORE the test was executed. Partially caused by using imprecise language "we seem to have lost all spacecraft telemetry just a bit ago" rather than an accurate timestamp.

A cautionary lesson in properly checking how exactly events are connected during an incident. Easy to look at two separate signals and assume they must be causal in a particular direction, when in reality it is the other way around.

Issues with GNOME come down to three inter-related issues.

* Configurability - GNOME goes out of it's way to remove any configurability from their DE. First they move settings to obscure places, next they remove them entirely.

* Compatibility - GNOME devs don't provide solutions for common use cases like window positioning or screen capture (yes I know that screen capture is now supported, but it's a compositor specific implementation rather than actually standardized by Wayland), at the expense of end users with those requirements.

* Consistency - GNOME seems to go out of it's way to do things differently from other mainstream desktop platforms. Windows does typeahead search, macos does typeahead search, KDE does typeahead search, GNOME does their own weird recursive search instead.

On their own each of these isn't a dealbreaker (I can deal with weird defaults if I can change them, I don't need as many settings if the defaults are less weird and don't break my software). But all three together is too much - GNOME looks like they are sitting in an ivory tower trying to dictate their opinions on desktop design to the world while having sub 1% market share. People won't drop window positioning or screen capture just because GNOME devs say so - they'll just not support Wayland. I know at least one real world person who swore off desktop Linux as a whole after Wayland screen capture broke at a critical time.

Surely nobody becomes a professional chess player because they think it will impress women.

The context here is somewhat different, given that Microsoft are essentially offering to roll out the red carpet for them.

The control of the supply si with Microsoft, who are likely falling on Sam’s side here.

Same company that completely missed the boat on mobile not that many years later. Intel have consistently made serious mistakes in their strategic direction. Fumbling 64bit, turning Apple down on mobile, missing GPU/AI.

They are basically just building a better version of the same product they were selling 20 years ago… so much opportunity missed here.

Apple's ARM switch worked because they have tight control over the whole software stack, and actually worked really hard to provide transparent support for older x86-64 software. Windows for ARM has none of this support and has basically zilch market share as a result.

If Microsoft releases an equivalent of Rosetta at the same level of quality it will be a different story. But I can't see what influence Nvidia has over this?

GPS can tell you exactly where you are, and nothing more. It can’t tell anyone else where you are, it can’t teach you to read a map if you don’t have the skills. It can’t tell you the best route through dense jungle terrain if you don’t have the skillset.

From the article:

> Again please note that a single binary can be counted multiple times, so the sum of the binaries in this graph is greater than the total number of binaries

So even if a binary only uses a small shim of Objective-C, it'll still count towards the Objective-C number.