out_of_protocol

*for a brief moment it actually runs.

from the point of the dev - work done on the port will rot very soon, return of investment is really low. Also, the studio may not exist at all by time changes will be necessary - as fast as few days after public release nowadays :(

Why bother with macos version at all then? Soon current version becomes unusable as well, and needs windows fallback to run since macos version is useless

It trades something fungible and incredibly cheap (CPU)

it could be RAM-bound, which is very much NOT cheap nowadays :)

There's a lot of places without fiber, e.g. all the ships/jets etc. there's a lot of low-density areas, there's islands with no internet or VERY expensive internet

6. You can make money without doing evil.

You can but well, it's more profitable the other way around....

On Android, opera browser has text-wrap which fits text into screen on any zooom level. Dunno how people live without this feature

I blessed to live in a country that uses kilowatts. That works wonderfully (and advertised as such) for AC units

Did anybody compared these directly using exactly same prompts and harness? I assume V4 Pro could be real frontier model, and if it's true, it'd be better to use it in automation or routine steps instead of simple models (e.g. haiku or even sonnet if V4pro is better)

1) that's not an ORM

2) after ~8 years of using it, i find it ergonomic, light on congitive load and good for long term support

Elixir is very ergonomic when it comes to concurrency, e.g. parallel-map example:

    1..10
    |> Task.async_stream(fn x -> x*2 end, max_concurrency: 2, timeout: 7000, on_timeout: :kill_task)
    |> Enum.to_list()

Golang has its positives but you also lose a lot. Whole ecosystem is not comparable, like "debug live production cluster" is one-command away for Elixir vs "fuck you" for Golang

Django is not very different than Rails and imo much less ergonomic. Many issues are still there like hidden state/setup needed to call something

ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO, but not everyone shares the same feeling.

Well, depends on what you do. Ecto is closely follows SQL logic and allows to translate weird sql queries into code directly. All queries are explicit, e.g. you either do preload(...) or can't access nested records at all, no chance of N+1 by design.

Changesets are also different and are just functions you can define as needed.

    defmodule MyApp.User do
    ...
    def changeset(user, attrs) do
        user
        |> cast(attrs, [:email])
        |> validate_required([:email])
        # This matches the error from the DB uniq index to the :email field
        |> unique_constraint(:email)
    end

I'd say Rails is faster than Phoenix (as in development speed) only for the first day or so. After that you'll stumble upon impicit logic, method-missing and this kind of stuff, which will require more time to figure out how it works. Elixi/Phoenix is more exlicit in that regard, making long-term support (as in anything past first week) a breeze. No hidden state, no figuring out where ModuleName.method(params) is coming from, no need to setup stuff to launch said method (just pass right arguments). The only downside i see is smaller library of ready to use packages

Probably going to be replacement rather than direct recompilement of structs. I imagine all sorts of corner cases are lurking around if you swap implementation around, e.g. if someone force-pushed unknown key into a struct at runtime. Would be nice to keep current struct syntax though with the only difference in declaration

i suspect a lot of tools will try to fetch the url without explicit user action (e.g. messengers do that kind of crap). Gotta be hard to keep keys non-revoked, which is a nice side-effect

If you don't use heat pump (which can have 300-500% efficiency), whatever you plug into a wall socket will produce heat at exactly 100%. So the real choice here is either monetize what you are doing with electricity or using a heat pump

1) they do protocol sniffing, and any inconsistency (including statistical) gets you blocked 2) "white list mode" which engaged sometimes (poorly implemented atm), means nothing goes outside of country at all (means 99.9% of everything is broken). They really want to become North Korea soon

How are you suffering equal heat stress from being submerged in moderately warm water

by the rules of this universe, you can't survive being submerged in 40C water for a prolonged period of time (even 37C would kill you as well), because humans produce heat and if you can't dispose of it you'll overheat and be dead soon enough

Humidity is the key, Finnish style sauna is low humidity+ high temperature (85-115C is OK i think), while Russian banya-style is low temperature (60-80C with high humidity). Both of them produce about the same load on a human

* VP9 where AV1 is not available (default YouTube codec, almost universally hardware-supported). Also universally supported .webm is vp9+opus - which mostly used as modern .gif

VP9 works well too and more supported (default YouTube codec)

Do note that in current economics 32GB of RAM alone will cost something like $400

This is a configurable setting.

Give me pointers please. Getting same headaches every day. Clicking on icon in dock, closing some window produces random results every time, across many, many apps

v7 exposes creation date, and maybe you don't want that. So, depends on use-case

fps getting increased but latency does not improve, and what's what important

its differentiation from Elixir is purely syntactic.

Well, there's also standard library, Erlang one is very messy while Elixir one is very consistent (and pipe operator - `|>` - enforces order of arguments even in low-quality 3rd party code as well, making whole language more pleasant to work with. Same goes for utf8-binary string everywhere and other idiomatic conventions

1. It's VERY common, sometimes pretending to be a .gif file. Many major image hosters are serving .webm even if users upload gif files.

2. AVIF is not a codec but a container. Webm also can contain AV1 video (but usually contains VP9). Also, difference between VP9 and AV1 is not that huge to be noticable on small gif-like animated pictures

Why .avifs when we have .webm already? Seems like overcomplicated replacement for already existing de-facto standard.

Windows 7 was effectively just vista but enough time had passed that the required hardware to run it was easy to get a hold of.

Not really, Windows 7 had a lot of work poured into it, fixing Vista issues. Even first public betas of W7 were more polished than any of Windows 8..11 releases. That includes work on minimal amount of "noise" notifications, driver issues, speed, design etc

Any favorites for "ebook into an audio book" process? Both model and software