I wasn't sure whether to agree with this or not, so I finally took a slightly closer look at Mojo just now.
This depends on how they license it going forward, and whether they make it open, or use being a superset as a way to capture then trap python users in their ecosystem, and I don't think we have a certain answer which path they'll take yet.
The way they let you mix python compatible code with their similar but more performant code [1] looks interesting and provides a nice path for gradual migration and performance improvements. It looks like one of the ways they do this is by letting you define functions that only use typed variables which is something I would like to see make its way back to CPython someday (that is optionally enforcing typing in modules and getting some performance gains out of it).
Stuff like this is why I can not switch to Apple, I would not expect or even think to look up which Macbooks can support at least 2 displays if they otherwise had decent enough specs for them. Who knows what else I am failing to consider?
I don't want to waste time migrating to a new system, only to find out I need to return/resell it, or later down the road find out another arbitrary/artificial limitation Apple has set that I either have to find a work around for or suck up until I can switch machines again if none exist.
This is unfortunate since there are some features that have made it very tempting to switch.
> Economies of scale. In particular, often total costs are a combination of fixed and variable costs. The more output, the more the fixed costs can be amortized, lowering average cost.
Except that after a certain point total costs increase again as the raw inputs become more scarce and expensive to obtain.
Yep, there would definitely need to be some regulations to prevent that sort of thing as well. I could see this becoming a business where companies are paid to take on this liability of distribution for copyright holders that meets some minimum defined threshold. Ideally it would be as seamless as the prior service if locked, or just reasonable download speeds if DRM free.
Yep, and if they want to end distribution altogether or start fresh and still keep copyright, they could distribute DRM free copies for some minimum time frame.
If the provider made it available for purchase (not subscription), the liability should go to them first to make DRM free copies available for those who purchased it before shutting down the service. If they are unable to do so, e.g. a sudden bankruptcy, then the liability could go to the copyright holder to find another provider to continue the service and transfer purchases, or provide DRM free copies (either should not be a problem if they are still making money from the given IP). In the event they are no longer making enough money from that IP and wish to just rid their hands of it, it becomes public domain.
Then they can be blocked from selling the rights without the liability of maintaining the service being attached. In order to end the obligation of maintaining the service, DRM free copies must be provided to everyone who purchased the content for some minimum time frame. Failure to do so puts the work in the public domain.
At the very least I would also accept a DRM free copy being provided to everyone who had purchased it (e.g. at least one year or so to download it), and in failure to do that it becomes public domain. Anything less and we basically just end up with the classic xkcd situation https://xkcd.com/488/
pokemon 1st gen had 151 pokemon, making it a pretty recognizable number for pokemon fans, and nothing else of comparable notoriety for 151, and the word choice of "evolve" plus the added emphasis of the quotes in the article, I admit it was subtle and may not have been intended, but my mind instantly made that connection, but on second thought I guess they could have also simply intended "evolve" as a subtle science pun as well
> After 151 years ... needs to “evolve” beyond its
I can't be the only one who noticed "151" and it definitely sounds like the author was alluding to it (pokemon) as well. Coincidentally Popsci and Nintendo Power were the only magazines I ever read and owned physical copies of.
Same here, especially since most of the time it's an unhelpful answer that dodges the actual problem or generic advice that doesn't apply, then they mark it as solved.
Which then furthers the question, why? I could understand the odd person just trying to be helpful because they had the same problem, found the post with no solution, figured it out, then answered with theirs, but for the ones who seem to spend countless hours ranking up, either by gaming it, or the few actually being helpful, does it lead to a chance of being hired or something?
Creating a system like that almost feels like it should be illegal, almost like the companies that give extensive case studies for interviews and take the work with no intention of hiring the interviewees, or unpaid internships where they don't even bother teaching and just give grunt work.
> So you only aped in because you were hoping to get rich without doing any work, and then you fraudulently opened up an account on a shady ass centralized exchange when you knew you couldn't KYC, and got your pretend money stuck, and then when FTX fell over it turns out it was never really there.
> Cryptocurrencies are awesome. Greedy people who can't do research and complain loudly when their "get rich quick" schemes blow up in their face make everyone look bad :-/
Normally I wouldn't acknowledge this, but I find your assumptions and accusations about me quite rude, for someone who has been on HN for at least 12 years you should know the rules. I simply stated the timeline of events as is, because there is no denying the connection between Signal and FTX through mobilecoin, and I only spent what I could afford to lose, I was well aware of the risks.
I for one will never donate to signal, and consider my $1000 (or $20k of never realized "fake" money, explained later) lost to mobilecoins to be my lifetime "donation" to them.
Short timeline of events from my side:
- Signal announces/endorses mobilecoin support, as their new and only cryptocurrency option
- I figure I'll get on it early this time after missing out on Bitcoin, despite Signal only supporting this in the UK (for now)
- Mobilecoin and Signal websites both mention FTX as being the only exchange where you can currently buy mobilecoin, never used it before but I go ahead, transfer $1000 worth (at the time) of bitcoin to buy mobilecoin
- There are currently no other wallets for mobilecoin (except maybe some difficult to use or obscure ones that looked sketchy? don't like leaving money on the exchange but didn't really have other options)
- Mobilecoin spiked on ftx, sold and bought back a few times, at the right time with some good luck, now have $20,000 of mobilecoin
- Signal finally adds support for mobilecoin in my country, proceed to try and withdraw it
- However, my country just announced legislation to require ID in order to buy/sell cryptocurrency, but it's not planned to go into effect for at least another 6 months or so, but FTX decided to start requiring it immediately and wouldn't let me withdraw without it (I could see they were still willing to take more deposits from me without it though!)
- FTX had trouble verifying ID, I already suspected what was about to happen, tried my best to get my crypto out but they kept having excuses, the ftx fall out and everything became known some months later
This depends on how they license it going forward, and whether they make it open, or use being a superset as a way to capture then trap python users in their ecosystem, and I don't think we have a certain answer which path they'll take yet.
The way they let you mix python compatible code with their similar but more performant code [1] looks interesting and provides a nice path for gradual migration and performance improvements. It looks like one of the ways they do this is by letting you define functions that only use typed variables which is something I would like to see make its way back to CPython someday (that is optionally enforcing typing in modules and getting some performance gains out of it).
[1] https://en.wikipedia.org/wiki/Mojo_(programming_language)#Pr...