559 karma · joined May 12, 2016
You could definitely use markdown within fields of a recfile. There would be some multi-line syntax you wouldn't be able to use, because it would conflict (e.g. '+' unordered lists), but other than that you could mark up text with Markdown, no worries.
It definitely seems like the kind of thing that could be independently invented. It's so based in random chance.
If you tend towards single-player, story-based games, like Red Dead etc., then maybe playing through it once and moving on is enough for you. Then again, maybe you'll want to come back to it in 3, 4, 5 years, and hopefully you'll be able to with Stadia, but with a disc/download you definitely should be able to.
On the other hand, if you play multiplayer, "live-service" games, as many are pushing to be these days, then you're already at the mercy of the dev/publisher to keep supporting the game so you can play it in the future. In that case, it become a question of who will give up support first, Google or the developer?
In either case, I think the Xbox Pass-style "all-you-can-eat" model is a better solution. No big, upfront cost for any single game, and you can still go back to something older, as long as it remains supported.
If your one-and-only screen is touch, you have to lift your arms up away from your buttons to press anything. No matter how much of an impost it is to have to look down a little, I'd say it's still less than having to lift your hand away from the buttons into your eyeline.
That way, people who want a video have a video (with the bonus of something to read-along to), and people who want text have text.
Such a law already exists in Australia, so I don't think it's out of the question.
> To be clear, the Windows Desktop component is only supported and included on Windows.
https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotne...
Yeah, you get a few cool features a bit early, but I just can't stand the instability anymore. Pluis, I'm not actually using any of the "Developer" features, so there's really no reason for me to not just run release.
By that definition, hacking a celebrity's iCloud account and leaking their nudes is a public service. I think that's a bit of a stretch.
I've always been a bit scattered across multiple cloud service, for various reasons, so I opted to use software that could sync with multiple and avoid installing so many clients.
That said, Dropbox's other maybe-not-quite "killer feature" is that it's exclusively intergrated into a number of applications for settings and data backup/syncing. In those cases, Dropbox's purpose is interchangable, but in practice it's not.
The other time I use Dropbox is for apps that use it as an intergrated way of syncing or backing up settings, such as MoneyDance[3].
[2] https://play.google.com/store/apps/details?id=dk.tacit.andro...
[3] https://infinitekind.tenderapp.com/kb/syncing-and-sharing-da...
I've never used the official app to connect to Dropbox, so now I guess I never will.
Plus, word on the street is Microsoft's motivation to move to Chromium was totally different to that: it was a performance decision. Too many apps were using Electron, and the only way to improve their performance was to intregrate it into the OS.
When a fix is fully rolled out (which should include Developer edition), then you won't need that (and probably should re-enable signature checking).
I'll probably turn 'xpinstall.signatures.required' back to true though.
The only way I see to get money out of someone for a product like Handsontable, while maintaining an open souruce version is by withholding some features + extended support. That's what they've been doing and they've said it hasn't been bringing in the return they need.
In Elastic's case, they have a product that is easy to monetize while keeping an open source version: you offer your product as a (hosted) service + extended support, so if people don't want to deal with setting it up themselves, they pay you. Docker seems to be a good example of this. The open source version is still fully availiable and can be used however you like, but comes without that extra support (and maybe a few features).
Instead, Elastic has stuck a bunch of proprietary code on Github, seemingly to bait people into use it, when they're not allowed to. Handsontable aren't doing anything like that. Once they go proprietary, they're archiving the repo. It's still there if people want to use it, but it's not being maintained. That's really no different to any other random piece of abandoned code on Github (of which there is plenty).