• 0 Posts
  • 78 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle
  • Define “freeloading” for me. They don’t have access to big social services (TANF, SSI, etc) due to not having documentation, roads are funded through fuel taxes as far as I’m aware (so if they’re pumping gas, they’re paying for the roads), dog parks are usually paid out of local sales tax (again, only as far as I know, I live in GA and we’re a fucked up state a lot of times).

    Income tax is a big one, but not on a small scale (like municipal level)… Hell, I haven’t ever had a local income tax that I can remember.




  • I remember it being iffy when I used it back then, the 8320 didn’t have GPS so it was trying to use cell towers to figure out the turn by turn. It was slower, but not as slow as the connection speed would seem because every page load wasn’t dependent on a thousand different CDNs and a hundred different trackers.

    A dedicated GPS was essential for cross country (if you didn’t want paper maps or printouts).


  • Do you mean the Cisco iPhone from the 90s or the Brazilian iphone from the early '00s? I’m totally just taking the piss though, I know you mean the Apple one from the later '00s but it wasn’t that rare to have mobile internet before it, they were just riding the wave that was already breaking across society.

    Apple had a major advantage though, lots of people were already eyeing their popular mp3 player, if a phone could be a phone, internet, and a good music player you can sync easily, it won for a lot of people. I couldn’t justify the price and really liked physical keyboards, by the time those became rare I disliked Apple too much to try them.

    Somewhere I have my old BB 8320 from 2007, it was awesome because it had WiFi so much better speed when WiFi was available.


  • I hated yaml with every fiber of my being when first had to use it, but I really wanted to use HomeAssistant and see what I could do with it. I hated it a bit less when I started using docker compose. I started loving it when I started using it as a way to explain json to non-programming IT types, trying to explain it without braces and brackets seems to get across easier. I guess its more human readable, but as a result formatting has to be spot on (those indents and spaces replace the need for brackets and braces).

    One useful trick if you truly hate it but need it, write it in json, then just use a converter to change that into yaml.



  • It will all boil down to what kind of maintenance is required. A robot for $50k would pay for itself in saved wages in under a year, even less if it collected tips. A lot of smaller diners (Waffle/Huddle/Waddle/etc) typically have super low staffing requirements (line cook + 1 or 2 servers per shift, occasionally more) and could totally use robots due to the simple layout and standardization of the restaurants.











  • Sounds good, but it essentially means you would then have to buy and maintain the method of power generation and delivery back to a company to sell it to someone else. I totally get remaining grid connected is important, but those grid connected systems are supplying a whole lot of power back to the grid. Perhaps if you generate more than you use, the power company should pay you to maintain your generators and infrastructure.

    Transparent pricing and not itemized billing could help a lot (and allow for better application of fees based on use case).