Uh, they spent hundreds of billions to get their flag ship products blocked by a democratic body with no possibility of recovering their capital except by concession of the people's representative?
I love the "year of the linux desktop" meme but even so I feel compelled to say it. Year of the Linux desktop?? You don't need a new machine if your new OS uses 1/4 of the resources.
They've got mine... Fly to Canada and your face gets scanned. I forgot this event and was surprised, walking through an American airport flying to another domestic location, that my picture and name appeared on an airline's screen without input. Not a government screen, mind you. I forget the exact context but the feeling persists. Very unnerving.
> Rayforce is a library you link, not a server you deploy. The C API is small enough to wrap from any language with an FFI.
I'm familiar with large-scale, commercial, client-server use cases for columnar analytics and graph traversal but what is the use case for an embedded server like this?
You can test this. All of them identify slavery as the root cause. Gemini says:
> The U.S. Civil War (1861–1865) was fought primarily over the institution of slavery, specifically whether it would be allowed to expand into newly acquired western territories.
> While you might hear people point to "states' rights" or economic differences as the causes, these issues were inextricably linked to slavery. The southern states wanted the "right" to maintain and expand slavery, while the northern states increasingly opposed its expansion.
> The rise of autonomous vehicles and technologies like hyperloop may make a major difference to the way we travel around cities.
Harvard University Professor of Economics everyone. When discussing new modes of transport the _hyperloop_ is the exemplar. A technology that does not work, can not work, and will never work.
And, of course, no mention of e-bikes which are cheap, proven, and have seen large adoption in my neighborhood at the least. But of course that might have undermined his point.
This should be read sarcastically. Its an idiom in the US. You state something you view as obviously true while qualifying it with "maybe - just maybe". Its commonly said in a comedic tone.
These sorts of articles have no value. The author is a "media entrepreneur". Being forced to read his opinion intermixed with out of context pull-quotes is not a good use of anyone's time. If Dawkins gave his opinion at length it might be worth reading but only if your goal is to understand something about Dawkins not about AI.
I would be interested to see a scientific discussion on what consciousness is biologically and if AI can fit that definition. But it would require someone with more credentials than a _media entrepreneur_ to pull off.
That is an unfair characterization of Zig. The OP correctly points out:
> Function signatures don’t change based on how they’re scheduled, and async/await become library functions rather than language keywords.
The functions have the same calling conventions regardless of IO implementation. Functions return data and not promises, callbacks, or futures. Dependency injection is not function coloring.
I agree. For my blog I don't apply CSS and prefer to let the browser's reader mode perform the styling for me.
But there are categories of application where that is not acceptable. The presentation is a tightly controlled aspect of the application's functionality. If you're designing an application with leptos or sycamore my suspicion is you would fall into the latter category rather than the former.
If your only target is web then there is no benefit other than a reduction in complexity.
For example, a "row" is not just a "<div>" tag. Its a div which horizontally fills its container. Centering contents with a "center" style attribute abstracts flex-box, browser compatibility, version compatibility, and the cascading behavior of CSS.
You move the incidental complexity of the web platform into the compiler which will always do the right thing. And in exchange you get the option to compile to a native or mobile app for "free".
Are there native frameworks which use XHTML? Regardless, a document language being used to construct complex, interactive GUIs is incidental complexity. XHTML can be a compilation target but it does not need to be a development target.
I really like these projects but missing from them is genericity. If you're taking the time to build a WASM app in Rust it would be nice if that app could compile to something other than WASM. For example, looking at the sycamore website's source I see p, h1, div, etc. What I'd rather see is "row", "column", "text". In their source I see tailwind what I'd rather see is "center", "align right", etc.
In other words, elm-ui but for these WASM Rust apps. Building a mobile app, a desktop app, and a web app, in my mind, should be accomplish-able given the right primitives (without requiring a JavaScript runtime be bundled). Rust's multi-crate workspaces make it a really great candidate for solving these cross-platform problems. IMO of course.
I'm talking specifically about this phenomena[1]. I wasn't agreeing with the GP that these policies are "oppressive". I'm only informing you that these states are not experiencing "explosive growth" and the downstream effects of that fact.
Both California and New York have shrinking populations according to Wikipedia. And even if the estimates are wrong and they do have growing populations you still need to consider the fact that the Southern states are growing much faster.
Federal power is shifting south. If you like the politics of New York and California that's a long-term problem that needs to be resolved.
> There may be an argument for leaning less on code review. When code is expensive to produce and is likely to stay in production for many years it's obviously important to review it very carefully. If code is cheap and can be inexpensively replaced maybe we can lower our review standards?
Agree with everything else you said except this. In my opinion, this assumes code becomes more like a consumable as code-production costs reduce. But I don't think that's the case. Incorrect, but not visibly incorrect, code will sit in place for years.