If a part of your platform is "No immigration" it becomes very difficult to distinguish that from "No immigration (because I don't like brown people)".
45 karma · joined February 28, 2023
If a part of your platform is "No immigration" it becomes very difficult to distinguish that from "No immigration (because I don't like brown people)".
Can we really not take a quick moment to say, "Maybe we can help our Muslim and Jewish friends feel more comfortable"? Your solution is really, "No Muslims or Jews in restaurants" rather than "Hey, if needed, we can just ask Kevin to toss the bacon in the oven."
The professionalism of ... Starbucks coffee shops? Are you for real? It's not a bank. Let people wear what they want and what makes them happy. You can still require people cover sufficiently for sanitary and safety reasons.
> On another note, seniority is a toxic, irrational policy
Yes. Agreed. But also, Starbucks has been hiring people specifically to "outcompete" pro union voices. A rush of new hires can destabilize organization efforts. Seniority for the purposes of protecting workers is reasonable. Seniority as the only criteria is not. It's a careful balance.
I dunno, they make me smile because they are so ugly/goofy.
1) The right to unionize without intimidation
2) Commitment to non-discrimination based on legal classes
3) Discipline happens on the clock and is free from harassment and abuse
4) Right to self-defense, covid safety, disaster/emergency pay raises, and zero tolerance for harassment
5) All firings should have a Just Cause
6) Allow workers to pick up shifts in non-union stores, transfer to them, etc.
7) Reimbursement for necessary equipment, limits on dress code
8) Full time for 32+ hours, benefits for 20 hours
9) New work cannot be added to job descriptions without negotiation
10) Schedule guarantees
11) Seniority will be used to prevent unfair working conditions
12) Workers in a store will have a committee to oversee working conditions in their store
13) No reduction in wages or benefits without negotiation
14) Unions have a place set up in the break room for union comms
15) The right to wear union pins/swag
Absolutely zero of these are "petulant", and we can argue about whether any of them are "counterproductive", but they all seem absolutely baseline reasonable to me.
I'm less sure about Apple, which might actually have more of a progressive streak in it (I'm simply not knowledgable), but the other two are pretty much standard exploitative mega corps.
I doubt that I'll have rich tooling and libraries to draw from when I need them.
If I build a game in C#, for instance, I have editors that can lint my code, perform intellisense, automate test generation, and a rich set of libraries I can draw from. If I don't want to write my own Hierarchical Task Network planner, I can use FluidHTN. Likewise, I can pull out my code from my project and modularize it for other engines/games -- maybe I've got a great state machine implementation or something I want to share. GDScript limits my reach.
The knowledge is also not particularly useful outside of working with Godot. Picking up C# from working with Unity, for example, translates to other domains easily if I want to change careers.
I also can't write my backends and supporting services in GDScript. If I wanted to , I could make my entire codebase in C# for both front end and back end code, simplifying my tooling and knowledge needs.
I don't want to be too down on it. I'm sure there are ways that it would save time. My use cases are much more about setting a high bar for ergonomics and engineering excellence for larger projects. I think that in my case, they've provided the Extensions and C# support route. (Though it sounds like getting those to work on all platforms is non-trivial today.)
Maintaining C++ support is expensive for an engine, just like maintaining any language binding. IMO, they should optimize for the most approachable/developer ergonomic language, which C++ definitely is not.
That said, I strongly disagree with their decision to simply build their own language. I think there are many languages that already exist that make better candidates for game development either because they are well known, well supported, or easily portable.
I want a base layer of one map, with an additional base layer (or raster data layer) on top of that base layer. It appears I can have one raster base layer, and any number of vector data layers on top.
Also, my tiles use -y, which I think is something I ought to fix (I just noticed this because I exported with the default output from ddb tile, which requires telling leaflet to use TMS or -y), so I can't just drop them in Felt.
I ask because I've got ~200 acres of forest I use a drone to survey. I generate a high resolution orthophoto, and I currently built my own site on top of leaflet using tiles cut from the large orthophoto.
I'm working with conservation organizations to try and restore some stream habitat, and being able to markup maps together would be incredible, but it looks like you are focusing on vector layers first?
Is it possible to provide my own tile server url? (e.g. I'll host the tiles on S3/Cloudfront/whatever, I just want to fancy notation/collaboration infrastructure.)
Edit:
Follow up -- I'm just one person who happens to work with various conservation groups to maintain the health of my forest. Typically, these groups are already strapped for cash, but it looks like this wouldn't really fall under 'personal' use because it's multiple people collaborating on a map? Very curious about whether you plans include a price tier for "I guess I want something like this but I'm also just like, one dude and not a business"
Edit 2:
Looks like yes, I can bring my own baselayer. (In my case, I have two base layers, one topgraphic, and an additional one that's the raster image, but it looks like I could create a similar experience on Felt?) So really, then the question becomes one of pricing for small uses like mine.