2,755 karma · joined October 9, 2012
(The problem space... of music theory. Or programming. Or "just writing our app" but in a way that generates reusable modules that are constrained to be small, well-defined in terms of types and functionality, and easy to test.) And learning to play the instruments all together in some kind of harmony, one that you can even type check, is just... chefs kiss
Some people think Ruby is the wrong choice, and others are building successful businesses on it as a foundation. Did they make this choice because of subjective tastes, or for practical reasons?
(And you can do this with Wasm, implement compilers in your Ruby framework in a way that's fairly unobtrusive, to take advantage of apps that were compiled in another language that isn't C... and likely to net you some type of benefits if not performance benefits – but the constraints are interesting. Did I mention that Wasm doesn't seem to have a string type, unless you count WASI?)
I mentioned Ruby because I'm giving a lightning talk on this topic this week Tuesday at GitOpsCon and a bigger talk at OSS Summit (one on Wednesday and another on Thursday...)
It's called "Exotic Runtime Targets"
Ruby and Wasm on Kubernetes and GitOps Delivery Pipelines
There's also "Microservices and WASM, Are We There Yet?"
You don't write a policy like this in such a way that it permits people to use the mark for just anything. It needs to be restrictive, at least a little bit. If it's registered then it needs to be protected; if you allow the indiscriminate use, you lose the trademark (and then just anyone can call their copier a Xerox machine on the package. Now if you're Xerox Corporation you actually do have a problem.)
Then again, I am a Rubyist, so I just went and checked on what trademark policies the Ruby language has, and as it turns out (unless I missed something) there are none. There also isn't a Ruby foundation – there's Ruby Central, the non-profit responsible for organizing the conferences (those are RubyConf and RailsConf) but they don't exert controlling authority over any community outside of the cons. They don't own any trademarks as far as I can tell. Maybe don't need this at all.
There is a Rails Foundation. Another example, not a language but: DHH owns the "Rails" mark and the trademark policy is this extremely reasonable one-pager (that also provides some specific real-world examples of what types of abusive uses it is intended to prevent. It's clear enough to me why we can't have unauthorized "Ruby Rails" dolls for sale by just anyone.)
https://rubyonrails.org/trademarks
I don't know how similar Rust Foundation is to Rails Foundation, but if it is too similar then I think I may begin to understand why people do not like it so much. No offense to DHH.
It does feel kind of circular. "Why is there a trademark policy?" Because we have this trademark and we don't want to lose it. "Why do we have a trademark?" To be held in trust by the foundation. Why do we have a foundation? To protect the interests of the community.
Well, if the community seemingly hates this new policy so much, are we doing that? ---
There is a third option though, you didn't mention: the Rust Foundation could actually listen to the community's feedback and draft a new proposal. I'm sure they won't let their mark get invalidated. I'm less sure they will listen now. (People all seem to have made up their mind that no compromise is possible, from where I sit.)
But maybe Ruby as a counter-example is more helpful than I thought. What company or collective stewards Ruby on behalf of the Ruby community? There isn't one, at least not officially. I used to think of Heroku as the company. Matz, the language's creator was employed there as "Chief Architect of Ruby" – is he still associated with Heroku/SalesForce now?
I don't know. I tried to find out if that is still true, all I found was a Wiki article that says he works somewhere else today. It's unclear if he still retains the title and position at Heroku/SalesForce.
So maybe Ruby didn't need a foundation, or maybe it did. Look at Heroku now. If Ruby was counting on their support, I think we'd all be in some kind of trouble. Maybe we are in trouble. I don't know how you feel about Ruby, but I like it! And I don't feel in trouble, that's good for me, so maybe I see your point.
I hope that we get to have more cool events where practitioners can meet up and advance the state of the art for their favorite language. And I'm frankly not sure if any of this information makes me more or less interested in using Ruby or Rust today. I think I'm fairly indifferent about it all. I don't want to get sued, mainly.
So I guess I do at least understand "Why CrabLang" then.
https://blog.rust-lang.org/inside-rust/2023/04/12/trademark-...
Registered trademarks have to be defended, if you don't defend them they can be invalidated. Forking the language is certainly one kind of feedback. But I get the feeling that most people who have a problem with this new policy would rather that there was no policy at all, no enforcement. I don't think that's very realistic.
And with the difficulty going up, the likelihood that you'll do this when it's needed and makes sense to do goes down. I can't tell you how many times I said "I need a website" and didn't end up posting one, because we didn't have a ready answer to this question, and nobody could be bothered to go out and build one.
Just a simple one page website. I can think of at least three "easy" ways to do it (and that's my whole problem in a nutshell, thanks for coming to my TED talk.)
As far as risks go, increasing UI premiums is one risk; it might be easy to invent a valid cause for immediate termination when someone gives notice, but also quite transparent in terms of ethics as you say. Concretely, that would also be leaving employers at a greater risk that word gets around with the remaining employees, and then you likely won't see employees giving notice anymore, or affecting morale of the remaining employees, or what else.
https://www.shrm.org/resourcesandtools/tools-and-samples/hr-...
To be fair, I'm pretty sure that I won't find the precedent I'm looking for in my own state either, but the link above is interesting: if your company has a policy that employees must give notice to quit, whether it was legally enforceable or not, with a termination after notice is given that policy could be used as evidence against you!
I guess it's a good idea to have a firm grasp of the law and review your own company's policies regularly, to be sure they align with the law! For another example in the same vein, I thought that only California made non-competes illegal but there are at least two other states, and it may be illegal to try to enforce a non-compete at a federal level soon.
https://www.foxrothschild.com/publications/ftc-proposes-rule...
(Not that this has anything to do with notice or unemployment...)
https://www.hg.org/legal-articles/fired-after-giving-notice-...
I'm pretty sure this lawyer knows a thing or two. And anyway, nothing is open-and-shut. Giving notice isn't "cause for termination" by any reasonable standard.
We were talking about risks. You can be pretty sure, and then a judge rules against you. Are you willing to take that risk? (Sure, maybe you know a judge. Or you live in a state with fewer worker protections. IDK, but I'm not making this up, and laws vary from state to state.)
It's bound to be cheaper to pay the two weeks than to pay the increase in unemployment insurance premiums for every remaining employee in perpetuity. In that sense, it's short-sighted to not pay you through your notice period.
Just set your VPN to an EU zone country and google "unlawful termination" if you're from the US / set your VPN to US if from EU, and read for some eye-openers!
(Ron Howard interjects... "They did not, in fact, wind it down.")
When I was using Cucumber, we almost picked up Turnip to solve that one.
For anyone that doesn't know Cucumber, you have one global context for all expressive sentences. So if you say "I click on the big red button" then there has to be one reliable way to detect the big red button on whatever page you're on, and it has to be the same way in every context.
In Turnip, you can declare contexts (like namespaces or modules) that allow you to have the same expression mean different things in each context. Only problem is, Turnip is even more obscure than Cucumber, and even fewer people know what it is, let alone having used Cucumber well enough to understand what all that means and what Turnip is for.
The other problem being, having a single global context for understanding the meaning of words arranged into sentences was a very powerful tool for promoting reuse and expressive clarity: if you found yourself using the same utterance in two different contexts, it was expected that you'd clarify so they could be distinguished and understood separately in a context-free grammar.
Not needed anymore in Turnip, unless you're diligent about reaching for the existing modules that you've created. (On the other hand, having your test utterances sorted into modules makes it a lot easier to reach for them, among related utterances...)
The parent comment had multiple assertions in it, so there's literally no way for me to know what you meant by "no it's not" until you told me.
> Vinyl chloride exposure is associated with an increased risk of a rare form of liver cancer (hepatic angiosarcoma), as well as primary liver cancer (hepatocellular carcinoma), brain and lung cancers, lymphoma, and leukemia.
If there's some fact in the parent comment which is in dispute could you please be a bit more clear about what it is? This is a very unhelpful comment from you.
A good rule of thumb is when you find yourself making "obviously bad decisions" because you know as a result the metric will go up, not because a generally favorable outcome for the business is expected to be the result, then you might be a redneck middle manager driving the metrics.
No one should generally exercise tunnel vision and you should not be completely focused on metrics. (Although it might be OK to have one person in the business whose job is to maintain the tunnel vision, if you're telling the whole company to do this then you are likely creating blind spots that will come back to haunt you.)
If you focus on driving up the metrics it can be at the expense of the vision. The business is not the metrics, and the vision is not fully defined by the metrics.
I hadn't seen either of these, and I didn't think I was interested in ML, until I got to the Natural Language Processing section, this is a great article!
Happy Ruby Upgrade Day!