Hacker Newsnew | past | comments | ask | show | jobs | submit | paramk's commentslogin

Here is a NYT article about the creator - https://www.nytimes.com/2022/01/03/technology/wordle-word-ga...



Looks like this script is not working anymore. I wanted to try the script when I saw this couple of months back in twitter. And in the process downloaded the whole catalogue.


Will this mean Keybase will be killed in the near future ?

From the blog

Initially, our single top priority is helping to make Zoom even more secure. There are no specific plans for the Keybase app yet. Ultimately Keybase's future is in Zoom's hands, and we'll see where that takes us. Of course, if anything changes about Keybase’s availability, our users will get plenty of notice.

So, our shortest-term directive is to significantly improve our security effectiveness, by working on a product that's that much bigger than Keybase. We can't be more specific than that, because we're just diving in.


> Will this mean Keybase will be killed in the near future ?

Absolutely. This was clearly an acquihire.

I copied all of my data out of my keybase folder today and I'd suggest you do the same.


So Tesla is doing what Clayton predicted twenty years back.


I don't know if he predicted that electric cars would follow the disruption pattern, but yes Clayton's theory seems to apply here in some sense.


Man's Search for Meaning by Viktor E. Frankl

This is supposed to be the author's memoir but it is more than that. Read it and it will change the way how you look at your own life.


So does this mean sooner or later we will be seeing the end of Cygwin ?


Scala ?


All we need is higher kinded types and implicits.


Higher Kinded Types, yes, but implicits... Yuck. Scala has definitely proven them as a failed experiment, I hope we will never seem them again in languages going forward.


Implicits are tricky, but they are the best way I know of to solve the problems they do. Other languages (JavaScript, Swift, etc.) have essentially open classes, where attachment of additional functionality to a type impacts a program globally. Implicits make it much easier to scope these extensions.

They are also quite useful for wiring up context (take Akka's ActorSystem, for example) at the declaration level, so that the bodies of your classes and functions only explicitly talk about your domain objects, rather than framework machinery.

They're also a big part of the power behind projects like Shapeless, which are quite useful for scrapping boilerplate.

Most controversially, they are also used to implement implicit type conversions. Modern idiomatic Scala discourages this, but it can sometimes be helpful.


I really like Scala. It is a really interesting language, and a productive one for me to program in. However, I agree that implicits are a bad feature. 90% of the confusing bits of Scala are because implicits exist and are, well, implicit.


unless, you're proposing a global implicits dictionary a-la Haskell, leave them alone, I much prefer to give up subtyping...


Exactly!


These stories depends on whether you are using PayPal as seller or buyer. Usually buyers don't run into these kind of trouble. Also there is dedicated website to share PayPal horror stories. http://letskillpaypal.com/?page_id=40


Ubuntu 14.04


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: