Hacker Newsnew | past | comments | ask | show | jobs | submit | korm's commentslogin

It's interesting to see UK-based influencers all citing these weak studies (internet surveys) about how social media is not so bad for children, or bemoaning the huge loss for children whose access to educational videos will be cut.

While the financial motive is clear, they must all believe it to an extent, because social media made their careers and changed their lives.

The reality is that the vast majority of kids aren't interested in learning video editing or movie directing, they are mindlessly consuming AI-generated videos and similar content served to them. 30-second videos on random facts sprinkled here and there aren't education.

Not that I think this ban will help, but downplaying the harm to children is a bit too much coming from people with ties to these platforms, like the author of this article.


>> The reality is that the vast majority of kids aren't interested in learning video editing or movie directing

Also the idea that they can't do these things without social media or YouTube is absurd. The people actually interested in learning something new will go down even deeper rabbit holes, try things themselves, and come out better than they would have following some YouTube tutorials.


It's not that people can't learn something from youtube, but that's not where most of people (not just the children) are spending most of the time. Just because someone watches a few videos about something useful to them that doesn't mean they aren't also being exposed to things that are harmful to them.

There are a lot of benefits to social media, and it could be a positive thing with fewer downsides, but there are basically no regulations to stop platforms from exploiting and harming children. The industry also refuses to regulate itself and prevent harms (many of which they created/cause in the first place). Parents clearly need to do a better job protecting their kids, but I have to admit that it's difficult when their children are being targeted and manipulated by companies with trillions of dollars while parents have to spend most of their time working just to keep their kids housed and fed.


The point is. I’ve heard all of this before. Does anyone else remember being 15 and having every adult nearby tell you that staring at a screen for 6 hours a day is going to destroy my eyes and my life? I can tell you it’s worked out pretty well for me.

Of course I agree the pointless AI generated shit is a massive waste of time, but it doesn’t really matter what it actually is as long as it allows them to connect over a shared thing. I think it’s far more important we ensure there’s spaces for kids to meet that are not purely digital.


I had a kind of social media when I was a teenager. It mostly involved dialing into a BBS or two, and its easy to think that it was harmless because it was a positive thing for me, but even I have to admit that there were dangers and even though those online places were similar they were also very different. Social media platforms are designed to be harmful in ways that a BBS just wasn't. There were no algorithms trained on data collected from multiple sources and focused on driving endless engagement. There were no people being paid to pretend to be regular users in order to secretly push products on me. There were games, including some that some parents would probably find objectionable, but they didn't constantly nag at me to buy things with real money (or virtual currency that could only be reasonably obtained with real money), and corporations didn't populate those games with brand ambassadors and ads.

It's too easy to look back and think "I survived online", but what adults today experienced online as kids is very different from what exists online for kids today. It's not just parents who are saying so. The social media platform's own research shows that it's harmful.


Yes, absolutely. But those people exist now, and you need to know how to deal with them because they're going to be a fact of your life going forward. The LLM's are going to tell you nonsense and pretend its the pure truth. The people you meet online are going to be mostly benign but interspersed with a few genuinely bad apples. You don't want all of that dumped on you at eighteen when you are apparently suddenly not a child any more.

I think it's much useful to teach kids early rather than late.


From an engineer working on this here on HN:

> ...while far off from feature parity with the most popular production browsers today...

What a way to phrase it!

You know, I found a bicycle in the trash. It doesn't work great yet, but I can walk it down a hill. While far off from the level of the most popular supercars today, I think we have made impressive progress going down the hill.


Yep, every SLA I've ever seen only offers credit. The idea that providers are incentivized to fudge uptime % due to SLAs makes no sense to me. Reputation and marketing maybe, but not SLAs.

The compensation is peanuts. $137 off a $10,000 bill for 10 hours of downtime, or 98.68% uptime in a month, is well within the profit margins.


It's not a transitive dependency, it's just literally bundled into nextjs, I'm guessing to avoid issues with fragile builds.


Gitkraken is the best, and I can't believe anyone would voluntarily use Sourcetree over it.

I've used gitkraken for over 9 years and it's great for both newbies and pros.

It completely solves the problem with new or intermediate devs, who are not used to working in a sizable team, constantly needing hand-holding.

Lots of people resist adopting it at first, but not one has regretted it so far. It usually goes like this:

1. "No I won't use it, the terminal is better"

2. Mess up

3. Finally give gitkraken a serious try

4. Realize they didn't really know git


GitHub has both webhooks and an extensive API. What you are describing is entirely doable, nothing really requires GitHub Actions as far as I know.

Most people opt for it for convenience. There's a balance you can strike between all the yaml and shared actions, and running your own scripts.


They must have not asked enough Leetcode Hard questions in interviews.


I am stealing this. Made my day :)


The mod_pagespeed filter "prioritize_critical_css" was released exactly 12 years ago in early May 2013. At least 3 more popular critical css tools were released the following year, integrating with Grunt, Gulp, and later Webpack.


It's a bit like the <center> tag. A codebase that's littered with stuff like "InlineStack" is harder to work with and parse because the resulting div soup still requires extra styling, which is now both markup and CSS.


Why is it harder to work with? It makes it immediately obvious what the visual layout is and what the purpose of the component is and a lot of time all you want to do is have a flex on a component and you don't need other CSS to warrant yet another CSS class. It's the same reason why utility CSS was created (eg <div class="flex">). It also saves you from having to come up with a semantic name in your CSS for every wrapper.

Compare the following:

    <Stack gap={2} direction="row">
       <Box>
         <Avatar />
       </Box>
       <Box>
         <Button />
       </Box>
    </Stack>

    -----

    <MyCustomWrapper>
        <InnerChild>
          <Avatar>
        </InnerChild>
        <InnerChild>
           <Button />
        </InnerChild>
     </MyCustomWrapper>


I think this looks way simpler

  <div className=“flex gap-2”>
   <Button/>
   <Avatar/>
  <\div>
Then just apply the box styles using *: selector or directly in the component


React was literally first created in ML out of the author's dislike of MVC, who preferred functional programming and immutability[0]. For a long time, react aspired for its future to be in ReasonML.

Hooks came as no surprise to anyone who paid attention, as the recommended way to write components since at least 2016 was in the stateless functional style whenever possible, and many of us used recompose[1] to simulate hooks long before their introduction.

[0] https://github.com/reactiflux/q-and-a/blob/master/jordan-wal...

[1] https://github.com/acdlite/recompose


Maybe I was not paying attention, this is of course a possibility, but until at least early 2019 the react website's main page was only mentioning the class-based "stateful component" as the way to write components.

https://web.archive.org/web/20190105060636/https://reactjs.o...

Although they were mentioning function components at the time in the documentation, I can't say how mainstream that was. Hooks were introduced in Feb. 2019.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: