South Carolina, in the US Southeast
Migrated from @0x1C3B00DA
South Carolina, in the US Southeast
BEAM is the VM that Erlang runs on. It also supports Elixir and some other lesser known languages
on-demand pods that travel on existing abandoned railways.
They’re reusing existing tracks.
I could see walking through a debug session document with a junior dev to guide them on how to debug classes of issues better. Or if they’re running into a bug and ask for your help, you could write out the first few debugging steps and let them take it from there. That might be easier to understand than “I’d check service X and see if it’s processing Y like it should or just passing it on to Z”. Having a defined way to explain how to debug an issue could be useful
that looks like a console
Not just looks, but provides the UX of a console. So you buy it, plug it up, log in, and immediately start playing. Even consoles don’t provide that streamlined UX anymore, but ppl want all the benefits console used to provide with all the benefits PC gaming provides now. But the key part is the PC benefits don’t get in the way of the ease of it. You don’t have to install or administer a linux distro, you don’t have to twiddle settings for every game (unless you want to), etc
What legislation like this would do is essentially let the biggest players pull the ladders up behind them
But you’re claiming that there’s already no ladder. Your previous paragraph was about how nobody but the big players can actually start from scratch.
All this aside from the conceptual flaws of such legislation. You’d be effectively outlawing people from analyzing data that’s publicly available
How? This is a copyright suit. Like I said in my last comment, the gathering of the data isn’t in contention. That’s still perfectly legal and anyone can do it. The suit is about the use of that data in a paid product.
I’m not familiar with the exact amount of resources, but I know it takes a lot. My point was about what specifically is in contention here.
Also, you were the one pointing out that this case could entrench “giant fucking corporations” in the space. But if they’re the only ones who can afford the resources to train them, then this case won’t have an effect on that entrenchment
Harvesting the dataset isn’t the problem. Using copyrighted work in a paid product is the problem. Individuals could still train their own models for personal use
I would argue that overriding methods on a prototype is not a hack. It’s equivalent to overriding super methods in Java classes, but using javascript’s prototype-based inheritance instead of class-based inheritance.
But I agree with your main point about choosing a language that lets the developer implement their solutions freely.
But public posts federating across the network isn’t an “experience”. It’s the basic functionality of the network.
for profit corporation being able to suck up your posts is probably what has many upset
They can already do that without a bridge. And it doesn’t “suck up your posts”. It works just like any other instance. They have to search for you and follow you. Then they receive posts going forward, but they won’t get historical posts.
I personally would block such a service
Good! You can do that and that is a perfectly reasonable solution. That’s part of what has ppl upset on the other side of this argument. All of this arguing and vitriol is happening over a service that you can block like any other fediverse actor.
Super agree with that. Framing this feature as specific to journalism was a poor choice. The feature is useful for any writer/blogger/joe schmoe on the web