Nope. These type of regulations looks good, but it's not fun or easy to do business in an overly regulated marked. If this continues, the US will improving financially faster than the EU. People are not likely to move to a worse economy because they value regulations like this.
> These type of regulations looks good, but it's not fun or easy to do business in an overly regulated marked.
This. Each regulation by itself sounds like something reasonable / potentially good, but trying to run a business in an environment like this is excessively complicated, and ends up being only something huge businesses are willing to put up with.
Yup. These type of regulations looks bad, but it's not fun or easy to live in an overly deregulated market. If this continues, the US will deteriorate in happiness faster than the EU. People are not likely to move to a worse society because they value regulations like this.
Ah yes, the bad-bad regulations of "do not spy on people", "don't collect and sell people's data wholesale" and "don't use undocumented blackboxes in surveillance".
Lots of companies work without collective agreements in Sweden though. Under law it's completely free if you want to do so or not. You could as well say that the unions are threatening the Swedish model due to taking this to such extreme levels. Especially as it doesn't seem most employees at Tesla want the unions involved.
The way unions work in scandinavia is that they are decentralized but supportive of each other.
IE as long as the workers don't form an local chapter everything is fine the problem if that when such a chapter forms and the company ignores it every other union chapter is allowed to refuse to deliver work in support of an company that choose to refuse/fight unionization.
So for there to be an conflict there have to be an meaningful chapter formed within tesla's employee base that tesla refuses to acknowledge.
Now again remember that this system is core to the "flexsecurity" systems employed by all of the nordic countries which is generally based on fair negotiations between equal parties(union and company) if Tesla manage to break that model they force the bureaucracy and state to take over and set highly rules without any concerns for local details they way it typically happens in France which is going to hit their profitability far harder then allowing unionization.
I work for a US company and I can tell that US management doesn't give a rat's ass on local customs until it bites them. You can raise and escalate and whatnot, they will still push the locals to implement the illegal/unacceptable stuff if not immediately then boiling the frog - anything goes until some agency or legal suit says whoa stop.
They are engaging lawyers and engaging with some of Sweden's most popular and powerful NGO's that's not doing nothing that's actively throwing money into a fight that's both hard to win and where the worst outcome might actually be for Tesla to "win".
Again the "laizes faire" no labor protections of America just don't exist in Europe the question is weather you negotiate with an equal partner made up from your own employee's or have the state bureaucracy micromanage local details.
So much "Network effects for me, but not for thee" vibes in this thread.
Lets be clear. The VC streak on this forum would viciously exploit any opportunity to wrest every cent out of any even ambiguously quasi-legal network-effect-if-you-look-hard-enough.
I personally get great amusement in seeing the shoe on the other foot for once. Rock on, Nordic fellows!
They do while conditions are ok, it seems like conditions are not ok for these workers hence they pushing for a CBA.
And while lots of companies work without a CBA here in Sweden, 90% of employees are covered by CBAs, so the vast majority are covered by one and Tesla fighting this by bringing scabs (a huge, huge no-no in here) is quite stupid. If they thought a CBA would be bad for business then strikes are even worse, it's their choice now to sign one or not with all the costs associated on not having one.
Most employees don't seem to be in support of the unions at this point though? It's a bit hard to tell as there are no official numbers, but from what I've seen it seems like ~90% or so of employees at Tesla remain at work. And there is a high demand for their services, so they could easily go to other companies for work if conditions are bad.
Not all workers have joined the union and wouldn't get paid by the union to strike. But unions use sympathy strikes against companies that might retaliate against their workers if they strike, Tesla has already made threats. So going by how many of the workers at Tesla are striking or not is not a good measurement.
The union is offering free memberships and 130% of normal pay. Tesla employees still don’t want to strike [1]. This is why the unions are using these extreme tactics.
No, you got it quite right I think. The government agency in question has a deal with Postnord (owned mainly by the Swedish state) to utilise them for all mail services. License plates has to be sent by mail. Postnord employees refuses to do so to Tesla. I believe they've also said they'd refuse to hand them out to Tesla should they come asking for them. In effect, not legal way for Tesla to sell cars in Sweden at this point.
At least not directly, if they sell via a dealership/importer who employs unionized labor they have no problem it's only direct from Tesla sales that's impacted but then again a big part of Tesla's model is of cause that they don't use franchised dealerships as middlemen.
I think it makes sense to think excel is sustainable on its own.
Also I've heard there are people in the US military who pretty much make PowerPoint slide decks all day.
I'd still package all of office together.
Maybe not excel on its own but I imagine office is already its own org inside Microsoft.
> Maybe not excel on its own but I imagine office is already its own org inside Microsoft.
You are correct, it has been its own org for a long time.
I don’t see the decoupling from the rest of MSFT ever happening though. Working with some of the Office codebase and some adjacent ones years ago, it is so tightly coupled on a technical level to many other MSFT products, it is pretty much impossible to separate. At this point, I wouldn’t be surprised if someone told me that there is some level of Xbox code integration within Office, and I am only halfway joking here.
AD integration alone is so fundamental, without it the whole product starts falling apart. Hell, some of the code in SharePoint has hard dependencies on rather ancient Skype/Lync code, and some pieces of core functionality code are still hanging onto files that were last touched 10+ years ago. It was kind of a bittersweet feeling to have to edit a piece of code and reading comments, and then realizing that the most recent changes to it were submitted by your manager around a decade ago, back when they were just starting out their career as a software dev.
And let’s not even talk about Teams, which has its fangs set extremely deep all over Office products (and beyond).
Fable is a very well put together game and I spent hours with it and had a lot of fun.
That said, a cursory comparison of the game features with the initial press releases from molineaux shows the kind of disconnect that exists from his ideas to his executions.
It's not bad to have a daydreamer setting the overall project vision, but anything he say at any time of the development process is to be treated just like that, as an internal vision document unrelated to the final product.
Sigh. I miss those stupid point and click adventure games so much.
I hoped for a closure to the monkey island series for so long. And after getting it I’m full of regret. Nothing they did would have made me happy. Nostalgia is what it is.
I've just removed sprockets from my Rails app and replaced it with propshaft, jsbundling-rails and cssbundling-rails. It took a couple minutes max. Now the "frontend" parts are no longer tied to the rails app, except you get a nice integration with rails assets:precompile and including the final bundle is as easy as ever with Rails.
I honestly can’t tell if your comment is sarcastic because my biggest gripe with Rails is that the asset story changes radically with every major release.
Starting with 3.2 and the introduction of the asset pipeline, every new version was “This is all about to change. A totally new way of using assets is coming.”
Every new version is supposed to solve all of the problems of the previous version. It’s exhausting to constantly change to keep up with the new One True Way™, only for it to be replaced with another assets strategy powered by a gem with a cute name.
RJS and Prototype, then UJS and jQuery, then Sprockets and CoffeeScript and Sass, then Turbolinks, SCSS, then Dart Sass, then Stimulus and Webpacker, then esbuild and TypeScript, then Turbo, then import maps but there’s also jsbundling/cssbundling, then Hotwire, then Strada, then “Turbo 8” and TypeScript is suddenly phased out because DHH doesn’t like it, and now Bun.
I’m probably leaving something out and this is certainly out of order. But my point stands: the prescribed way of handling assets with Rails is ridiculous.
I think a lot of communities assumed letting JS asset pipelines manage JS, CSS, and image assets would lead to a better future. Sadly that didn’t materialize and it inflicted a lot of damage on DevUX.
Today the perception is that the JS community doesn’t seem to care about providing a stable experience for those outside of it, which is why projects like Rails and Phoenix are successful with “No/Low-JS” features.
Where Rails screwed up is not updating their docs to reflect this new reality for a really long time. It wasn’t clear what people should be using. They’re still creating confusion by making it unclear if Turbo is for Rails or all web frameworks, which you’ll notice when you go to the Hotwire landing page and see no mention of Rails.
> But my point stands: the prescribed way of handling assets with Rails is ridiculous
What would the alternative be for a 20 year old project?
I think what we're seeing is a natural progression based on how the web changed over the last 2 decades.
I'd be more concerned if Rails didn't change and `rails new` produced a jQuery / SCSS / CoffeeScript loadout and made it difficult to use modern tools. Now it's easier than ever to plug in whatever front-end you want.
> I think your parent comment point is that they could have skipped half the changes and still kept up to date with frontend tech.
How tho?
Things naturally progressed from a lot of asset related things with few choices being baked into Rails to being more componentized but still tightly baked into Rails (Webpacker) to even more componentized and mostly decoupled from Rails (current state of things) to even more decoupled from Rails (Propshaft).
Current day if you want to use Webpack or esbuild or something else or nothing it's easy because Rails no longer cares. It only cares that assets end up in a specific directory. How they get there is up to you. The framework also provides value by giving you generators to tie things together based on the choices you want so you don't have to figure it out individually from ground zero.
If you look at it from that perspective I think things unfolded reasonably well.
Personally I didn't like Webpacker at all. Webpack was complicated enough on its own and then having to learn the Rails way of configuring it made it even harder. But I think it was a good tipping point to demonstrate that from a maintainer's POV it's hard and time consuming to create good abstractions over front-end tools on the back-end and from an end user's POV it's bad because of the complexity.
Being able to look directly at esbuild's documentation and apply it 1:1 is a much nicer outcome for everyone. Maintainers don't have to keep up with every change and users don't have another layer of abstraction to deal with.
It did take Rails a while to come to this solution but it's really good that they did. This is how I managed front-end tools in Flask and other frameworks for around the last ~decade. You have the framework look for assets in 1 spot and how they get there is up to you. It was easy for me to do that because I only had to make it work for my apps, my client's apps and the starter apps I posted on GitHub, but applying that to a framework that has hundreds of thousands of people using it is for sure a bigger project.
Gun violence and these explosions have been going up quite a bit last few years at least. Anecdotal (Sweden here) people in my closest circle feel a lot less safe, and less comfortable in public spaces, compared to a few years ago. Not to a huge extent, but noticeable.
