> Hasn't DeepSeek's novel training methodology changed all that? If the energy and financial cost for training a model really has drastically dropped, then frequent retraining including new data should become the norm.
Even if training gets way cheaper or even if it stays as expensive but more money gets thrown at it, you'll still run into the issue of having no/less data to train on?
Because you have two parties of HN users that happily flag, which is enough. Those who are Trump supporters and those who just don't want any politics / the discussions surrounding it on HN. ¯\_(ツ)_/¯
Doesn't seem to be a duplicate, so dang might unflag it and remove the filter if he sees the thread.
While I also agree with the sentiment that it's not the same, I think it's interesting that you use "googling" as a comparison.
Googling and extracting the right information efficiently is clearly a skill, and people do use it in wildly (and often inefficient/bad) ways. That might be less of an issue with your average HN user, but in the real world, people are bad at using Google.
Palword vs Nintendo is not a trademark case but a patent one. People in gaming are notably very much not in love of patents restricting what games can or can't do.
Also, megathreads are what you do when you want a topic to die on a subreddit. Especially now where pinned threads even have less visibility.
Their obviously bad faith poll after ending their "no moderation experiment" after not even two days (while announcing it for a week), also speaks a different language.
- the creator of the subreddit still seemed completely pro-Matt and also friendly with him
That said, bluesix seemed like a very helpful mod, so, still not great to see them delete their account. And also, some users are for sure in it just for the blood.
The obvious move on moderation side would've been to allow big news around that "drama" to have their own threads, to remove duplicates and have random opinion tweets, blog posts & influencer's thoughts in the megathread / a pinned comment on each of the "big news'" threads.
This is what most mods who wouldn't want to suppress the topic but keep the sub somewhat clean would've done. For some reason, that wasn't even up for discussion.
It was either a "we go on strike and stop moderating" (which ended quickly when it didn't result in the chaos they anticipated), megathread or complete ban of the topic for them.
And we will have to agree to disagree I guess.
Here's how I would summarize some parts of it:
- The moderators didn't want to completely censor or remove good faith threads, they just wanted to contain it within megathreads. this is normal on reddit. I disagreed with this and thought it would be better to have some threads on front page but limit the number.
- The mods didn't make an attempt to censor r/wpdrama from being talked about, they redirected users to it
- The users were fundamentally angry and accusatory from the get go which made it even more difficult to come up with solutions
- This is not how I remember old reddit nor the old internet. Back then we would have a civil disucssion with the mods about what things should be allowed or not allowed.
The mods could have literally done nothing and the majority of users (as proven by the unofficial poll) would have approved. The mods didn’t know how to moderate without being little dictators. Once they realized this they gave up and ran away.
Those 20 poorly written plugins make a good amount of money though, which is why many of those plugins' creators and affiliated "wordpress influencers" also do an outstanding job pushing the sentiment against more integrations into the core.
Payload 3 (currently beta) doesn't look bad, but a site still needs some work from somebody who can at least somewhat code, and it's not just installing wordpress, generatepress and ACF.
Mainly because they're relatively simple graphically but they want to run at super high framerates, so the bottleneck is the CPU feeding the GPU each frame.
Which is basically memory bandwidth problem, which a large L3 cache helps a lot with. I've seen the same things with ClickHouse, having a larger L3 cache and fewer cpu cores can increase performance significantly.
Doesn't a lot of optimization target making your code and data more cache friendly because memory latency (not bandwidth?) kills performance absolutely (between other things like port usage I guess)?
If something is in L3 it is better for CPU "utilization" than stalling and reaching out to RAM. I guess there are eventually diminishing returns with too much cache, but...
I certainly don't care to do it, but running FPS above your frame rate can reduce latency if the frame buffering policy is reasonable (or you don't mind tearing). The difference isn't very big, especially if you're at 240Hz, but getting stuff to the display one frame sooner makes a difference.
But I've heard of triple buffering setups where you're displaying the current frame, and once you have a complete next frame, you can repeatedly render into the second next frame, but the next frame isn't swapped. In that case, it's hard to argue for any gain, since your next frame is way old when it's swapped to current.
Some rendering systems will do double buffering where the render is scheduled to start just in time to finish with a small margin before vBlank. If you've got that tuned just so, that's almost the same latency benefit as running unlocked, but if rendering takes too long you have a stutter.
Even if training gets way cheaper or even if it stays as expensive but more money gets thrown at it, you'll still run into the issue of having no/less data to train on?
reply