Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JR
Posts
0
Comments
270
Joined
2 yr. ago

  • My take is that best case scenario you'd arrive roughly at the same time you left.

    If you have breakfast in London at 8am, then make it to the airport by 8:30, you're at the gate at 9:30 after one hour of security and controls, and you've made it exactly at the time when boarding starts, which usually is 45 minutes before takeoff on most airlines. You take off at 10:15, arrive at 11:45 (which is 6:45 local time), then still have to go through half an hour of border control and getting out of the airport, and then another half an hour to get to the city centre and have a coffee.

    You'd still arrive at about 8:30, but I don't see the whole ordeal taking any less than 5 hours.

    I routinely take a 1.5 h flight to visit my family and while I'm a fair bit away from the airport, I don't think I've ever managed to get door-to-door in less than 8 hours. 6 if we are measuring departures lounge to arrivals.

  • I hope AMD keep pushing to do things well, because right now the value proposition of anything with an Intel processor is more ridiculous than when Apple charges $300 for an extra 8GB of RAM. Their $600 processors currently offer performance on par with the entry-level Apple Silicon M4. Which is great news for Apple, but not for anyone who wants to use Linux or "the other Mainstream OS".

  • Something I find incredibly weird about US company culture is how they talk about overtime like it's a good thing.

    "Our employees worked weekends, days and nights to make this happen! We wouldn't have succeeded without people who are willing to give up their personal lives!"

    I hope they not only succeed but get shares. Doing weekends or nights for a company you don't (partially) own feels like a con.

  • I don't think anything with the word "intel" can be taken seriously in value comparisons...

    When I got my last laptop I ended up with a MBP because there were no high end options for Linux laptops with AMD. Now the options are better, but back then, the only realistic alternative to a MacBook Pro would have had a third of the real-world battery life if not less, even if I decided to spend £3k. That didn't seem like an acceptable compromise so there were virtually no laptops in existence that could compete with an M2 MBP.

  • Permanently Deleted

    Jump
  • How do people have the time to organise vigils and get into "coalitions" and politics in the workplace?

    Granted I don't work at Microsoft, but I feel me and everyone around me is overworked enough that when we have the time to stop working... We head home (or close the laptop if WFH) and rest, not engage in additional activities in the workplace.

  • We really need to think about a better name than "Early access". At this point I think I've used Lawnchair for about 5 years, 5 years after the initial event is only "early" in the context of geological eras.

  • It's not a waste of resources if you learn something. Think of this as research rather than product development. You can try many things (from VR, to miniaturised computers, to cloud gaming, controllers with wonky form factors...) to see what results in a good experience. You don't need to get anywhere near a full fledged product to understand those things, so the waste of resources isn't massive anyway.

    I'd bet at the moment people decided "this is useful, I even want this for me, so let's turn it into a product" the steam deck looked more like a screen, a gamepad and a raspberry pi all taped together or jammed into a 3d printed prototype chassis.

    If people have spare capacity to work on these projects, the material cost at such a point can be under <5k which is peanuts for a company like Valve.

  • To be honest I get your point. We use it at work for summaries of 70-page lists of software commits, and with adequate prompting to "understand" what's what in our codebase it works remarkably well.

    Granted it doesn't work near as well as a person who spends a month working on such a summary, but it does it in seconds. Then a person can work for a day on reviewing this and tidying up rather than wasting time trying to summarise 100k lines of code by hand.