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/)MO
Posts
0
Comments
52
Joined
2 yr. ago

Yes, please!

Jump
  • Lol, yes. I can't imagine that it would help much, but it would definitely be annoying. Especially for the parking lot. Imagine that instead of basically flattening the ground and pouring asphalt over it, you'd have to tear apart a thick bamboo forest yard by yard. Also they'd need to make really sure to remove all of the bamboo, or else it could grow back, maybe even through the asphalt.

  • I simply can't believe that they released the game in this unfinished state. Early access or a public beta would be understandable, but you just don't release a half-finished product promising to deliver the remaining stuff later.

    The Minecraft way where you continually provide upgrades for your game can obviously work, but in that case, the game is cheaper and the upgrades are free. If they were going that route, CS2 should have been a free upgrade of CS1 with all the features of the previous product and nobody would've complained.

    If you buy another full product, you expect another full product.

  • That's true. I think the sequels did a lot right. A woman as a main character was long overdue. The visuals are great, acting is good for the most part.

    But there's no overall story that makes any sense and it contradicts the previous movies pretty much everywhere. 7 wasn't very believable, but made at least some sense if seen on its own. 8 didn't seem to have much story impact at all, people seem to just solve short term problems constantly. And 9 could well be a parody. A parody with a very big budget.

    I liked the spin off movies (Solo, Rogue One) a lot, though.

  • You acquire skills and then start the business. Without skills, you won't know if the idea is any good.

    Like your idea could be to create and sell a software to design Lego builds, but without any skills in software development or law, you'd have no idea if that's feasible programming wise, how much work it would be, or if Lego might sue you for trademark violation if you do that.

    Ideas are easy, doing the stuff is hard.

    Obviously you can outsource some parts, for example you could hire a lawyer to make sure you violate no trademark law, but when you don't have much money, the reality is that you will start small and have to do most research and actual work (if not all) yourself.

  • I really liked his relaxing, calm MacBook repair and data recovery videos, where you could learn about soldering and electronics repair while watching. And I had no problem with a little bit of honest advertising for his own business.

    While the right to repair is important, his videos about it are a lot of rambling and complaining about the same thing again and again. The titles are also often misleading or click baity. I can't watch them either. I hope they work for the right people, though.

  • You're usually told to use pain medication as needed, but it can have side effects like reducing swelling, fever, blood clotting and so on, so I'd probably still ask if I can leave it out if I know I have a high pain tolerance.

  • The main difference is that when you compile a program for Windows, Linux etc., you have an operating system and kernel with their exposed functions/interfaces so even in a compiled program it's pretty easy to find the function calls for opening a file, moving a window, etc. (as long as the developer doesn't add specific steps hiding these calls). But in an embedded system, it's one large mess without any interfaces apart from those directly on the hardware level.

  • How often does branchless programming actually matter in the day to day life of an average developer?

    Barely never. When writing some code that really has to be high performance (i.e. where you know it slows down your program), it can help to think about if there are branches or jumps that you can potentially simplify or eliminate.

    Of course some things are often branchless, for example GPU shaders, which need very high performance and which usually always do the same things. But that's an exception.