• 15 Posts
  • 294 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle



  • I looked it up on the internet, e.g here it has only mean data: https://worldpopulationreview.com/country-rankings/median-income-by-country

    Maybe 5 is not the exact number but it should be in that range.

    I never said the quality is generally bad, but I think he misunderstands why other companies ask for details, that’s my point. If you don’t design something with enough details, you basically allows someone else to design it with your name on it.

    Do you think Apple just sends a vague sketch about the iphone to china and let them figure out the details? As a designer you shouldn’t do that, because if something wrong happens with that thing it’s your liability.

    He won’t tell the Chinese company what kind of welding should they use, so you can be sure they will use the cheapest method, because they also need money for food. If he would design the product correctly, with requiring standards, than I guess the price would be also higher, because now the Chinese company can’t use the cheaper option.


  • Well, I have a feeling that the fact that US median salary is around 5 times the Chinese is also plays a role here…

    So for the same job which requires a human you have to pay ~5 times more to be made in the US, and for a black coated box like the one in the video it doesn’t really matter if it will be sitting in a container for 1 week or 4 weeks, so that’s a reason as well…

    He speaks about in the video that the Chinese design details for him for free. But whose liability would be if that weld in the corner breaks? He will tell it was because the manufacturer used some bad welding practice, but he will have to pay for that. Good luck trying to sue a sweatshop in China from the US… The American company asks for details to cover their asses, not because they don’t know, so for a design failure they can point to the designer.

    I’m not a metal shop I’m a software development company

    This perfectly sums up. You don’t know what you are doing and the Chinese also see this, but they see it as an exploitable stupid American, who has no idea what he speaks about, so they can sell him the lowest quality product…







  • Afaik windows on arm is still very limited, a lot programs still only support x86.

    And touch ux on linux is not very convenient, I have a touch laptop and have used it with gnome for years, and it has a lot rough edges. Can a linux enthusiast use it? Sure. Would I recommend it to non computer savvy user? No, they won’t enjoy it.

    I tried xfce about a year ago on an old intel atom x86 tablet, it was not usable at all. I read Gnome is the most advanced in touch support, I don’t know how touch friendly is kde nowadays.

    So on windows a user would be limited to basic apps, android has much more options.




  • It definitely shows lake names, it’s just limited to specific zoom levels, e.g. here you should see all the names of the Great Lakes: https://www.openstreetmap.org/#map=7%2F45.064%2F-81.758

    The source code of the renderer is here: https://github.com/gravitystorm/openstreetmap-carto

    And there is an issue about displaying sea and ocean names: https://github.com/gravitystorm/openstreetmap-carto/issues/2278

    Rationale from @[email protected] as an issue comment:

    We need to be careful with these labels, for a few reasons. Using a single point to represent an ocean is quite an oversimplification! These points are also arbitrarily placed, so mappers could get into endless edit wars about where to put them. Many mappers will use them as “labelling positions” rather than ensuring the position has some kind of geographic basis.

    The Arctic Ocean label is a good example. From the overpass screenshot I assume the node is outwith the range we render. Do we want just the bottom half of the label showing?

    Normally oceans and sea labels are “hand placed” by cartographers, since the challenge of automating the label placement is so high. But we can solve the technical challenges here; while doing so lets remember not to end up rendering “labelling nodes” by mistake.