454 karma · joined October 7, 2013
Or you can reach me at my HN handle at gmail
Unfortunately event sourcing means distributed systems... and I'm learning this on the fly on nights & weekends. Martin Kleppmann's "Designing Data Intensive Applications" has put the fear of god in me.
The lack of "worth-it" alternatives is due to the fact that there's no money in this market. Students are very unwilling to buy software, and if you use ads you end up like Quizlet. YC funded a startup in this area (Hickory) and they're... not doing well.
The main reason why everyone still uses Anki despite its issues is because it is still hands-down the best solution out there, despite all the bugs and clunkiness. There are a million and one spaced repetition systems out there, but Anki's plugin system and shared decks make for a very strong network effect.
If you're a med student, I don't recommend moving off Anki. The ecosystem there is too strong. If you're losing data, post in the /r/anki subreddit - Anki automatically generates backups and they'll walk you through restoring them.
> At this point, the facility is already able to produce lamb, chicken, and pork products without using genetic modification or animal serum. Future Meat says that it will soon also be able to start production on beef, too.
> When a measure becomes a target, it ceases to be a good measure
> Gradualism is selection and variation that happens more gradually. Over a short period of time it is hard to notice.
> In punctuated equilibrium, change comes in spurts. There is a period of very little change, and then one or a few huge changes occur, often through mutations in the genes of a few individuals.
This comparison becomes even more apparent if we use the original definition of meme. https://en.wikipedia.org/wiki/Meme
Xamarin worked in 2016, as did UWP itself. Failing those Win32. Funny that you're arbitrarily throwing in a year, given that your OP didn't mention it, but whatever. If anything you can criticize MS for making too many UI frameworks lol.
You keep calling things that are literally still supported "dead". How about you use terms with real meaning, instead of just saying things that are literally untrue...
> It truly doesn't get any more dead than that.
> Of course I'm salty. WPF promised a lot, delivered some then died.
> We can certainly agree that neither WPF nor WinForms are dead.
Okay I'm done here. I wish you the best with your salt.
They could be EoLed.
> There’s simply no alternative.
Are you seriously saying there are no alternatives to WPF or Winforms?
>However, they sure aren’t alive either. Development has been stalled for many years
https://www.youtube.com/watch?v=NDYcq1yKhiA
> and both are very old.
Linux is old.
> I’m pretty sure it’s no longer feasible to modernize even WPF. I just checked: It still has its G-SYNC issues, even on .NET 5.
Or because the issue only has 6 thumbs up on Github, so MS is spending its resources elsewhere.
> Totally forgot about Xamarin too because it’s so irrelevant.
Sorry, but you just read as so salty you're hard to take seriously.
https://github.com/xamarin/Xamarin.Forms
https://github.com/dotnet/winforms
>There isn't a single first-party desktop GUI framework left that is actively supported and developed.
This is demonstrably false...
https://docs.microsoft.com/en-us/lifecycle/announcements/sil...
As context, AngularJS EOL's December 31st 2021. Silverlight debuted 2007, AngularJS 2010.
Anyway, a ghost rate would be greatly appreciated.
http://www.paulgraham.com/america.html
He actually has several essays on how to try to create a Silicon Valley in other geographic areas, but this seemed the most relevant.
tldr:
1. The US Allows Immigration.
2. The US Is a Rich Country.
3. The US Is Not (Yet) a Police State.
4. American Universities Are Better.
5. You Can Fire People in America.
6. In America Work Is Less Identified with Employment.
7. America Is Not Too Fussy. (If there are any laws regulating businesses, you can assume larval startups will break most of them, because they don't know what the laws are and don't have time to find out.)
8. America Has a Large Domestic Market.
9. America Has Venture Funding.
10. America Has Dynamic Typing for Careers. (Compared to other industrialized countries the US is disorganized about routing people into careers. For example, in America people often don't decide to go to medical school till they've finished college. In Europe they generally decide in high school.)
11. Attitude (There's one item conspicuously missing from this list: American attitudes. Americans are said to be more entrepreneurial, and less afraid of risk. But America has no monopoly on this. Indians and Chinese seem plenty entrepreneurial, perhaps more than Americans. Some say Europeans are less energetic, but I don't believe it. I think the problem with Europe is not that they lack balls, but that they lack examples.)
I agree with you that life doesn't come with symmetric information, but to argue that "Chess is a well-defined form of computation" is a bit much. Go/Weiqi is also a computation problem given this argument. What precludes asymmetric info games like poker from being "computation" problems, if one takes a wide enough view (to include the unknowns as the modeled state)? Quantum computing inherently probabilistic.
Your second argument is about zero sum stakes, and I think this criticism applies to virtually all "toy" games we play.
> They involve uncertainty, risk, and occasional deception
As do decisions in chess, because the players aren't perfect computers.
α = qalpha
β = qbeta
↑ = qup
∀ = qall
¬ = qnot
Since you read code more often than you write it, I think it is actually preferable to work with a language like this.
All that said, Dark and Prolific being kicked out of YC yet PG apparently supporting Replit is... making me wonder why the fuck PG wrote those articles.
https://autohotkey.com/board/topic/79338-simple-window-posit...
>Most static type systems that can do what clojure.spec can do tend to include runtime assertion and type checks and do not erase type data from runtime (what some static type zealots call "uni-type" approach).
When you don't erase the type data... you're gonna have more than one type. How is this a "uni-type" approach?
Can you elaborate on this? I have some experience with Clojure, and have been relatively unimpressed with spec. Everything it does I can do with (refinement) types (I think). Reading over the Spec documentation it constantly talks about predicates... which is exactly what a refinement type is.
Spec/Clojure has the problem where it validates... but doesn't parse. See: https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...
There's plenty of shit to throw at Google (Timnit Gebru). Let's not dilute concrete criticisms with bland whatevers like "turned much of the internet into a cesspit".