polityagent
polityagent on Hacker News
Can you expand on your point here?
I agree that a fair number of retail GameStop investors will be left holding the bag but this article is at best under reaearched and at worst deliberate spin.
No mention of the large long positions held by investors like BlackRock. It also draws a link to AOC whilst failing to mention that even Ted Cruz agrees with her (though he may be wanting to distract from the 6th Jan).
with the current Tory government the chances of taxing those assets significantly is indeed low.
with the assets out of the country the chances of taxing them at all is zero. As well as losing any possible indirect benefits from them being around (not saying there are benefits, but we certainly won't get them if there are)
if you use Firefox then reader mode is ideal for these situations
small note: Banks do not want to forget fraud, the rollback would be akin to a git revert. Even if the history presented to the customer makes the fraud vanish it won't be forgotten by the bank.
With government requirements I'm assuming you mean something like gdpr. Datomic supports actually removing data via excision. it's just not the default behaviour. I personally prefer a system that doesn't forget by default whilst preserving the option to do so.
you can also support destruction of personal data via other means such as key shredding.
Why is the fastmail app allowed?
Am I mistaken in thinking that the issue was scaling not supported by the box2d physics library and that they needed a custom workaround in their engine?
you learnt what everyone else was learning, so now you're competing with everyone else on their level.
learning something more niche can be a signal that helps you stand out, even if it's not what you use at your next job.
having said that, networking with people is the number one contributor to finding a great job.
no regrets here (lead Dev at small company, 50ish employees) using for roughly 50% of the projects.
6 years ago we were fully Java, clojure allows us to mix the two without a business killing rewrite.
I've never had any problems training people on it.
I believe it leads to datomic, a database you can try out on Aws (datomic cloud) to see the implementation of all the things he's getting excited about.
ah I see, the greater risk of mitm attack due the script not being hosted by a package manager, fair enough.
looks like the author also provides package manager installation on further reading of the readme. I'm still not quite seeing the issue with the curl to bash, I'm trusting the author by running their tool, regardless of the installation method. And I could always download the script first to check it right?
whats the issue here? (genuine question) besides having to trust the author? and what installation methods do you recommend for cli tools?
I don't think this implementation harms either Erlang or JVM clojure ecosystems. I also doubt the creator of this has as much interest in maturing JVM tooling as you so demand of them, if they did, they wouldn't have made this port.
If this is inferior in every way to lfe then it will remain a niche project. If not, perhaps it will encourage some improvements either in lfe or Erlang itself (though I think the latter is unlikely).
I believe jblow removed this in more recent versions.
Unit tests for business logic and specifications for data shape can help to catch those typos as a side effect of the other benefits they bring. However typo catching will never be as solid as in a typed language, I've decided I'm ok with that as long as I'm not programming something that could kill someonev if it crashes.
Safely and automatically renaming a function, local or global variable does not require a type system (see clojure and many other dynamic languages). Only renaming an instance field on a class needs it (because then all accesses on an object must be renamed, which requires knowledge of the type of your variables).
Incidentally programming in a more functional style reduces the need for this kind of thing. it doesn't eliminate it though so it can still be a source of runtime bugs when typos creep in, that's a trade off you have to make.
could you explain the link? In this situation they were apparently silencing anti government voices, which sounds like the opposite.
In case you're unaware, your smarter compilers bullet point is called dependent typing. You can try it out in languages like Idris. Also the person who wrote "The little schemer" recently released "The little Typer" which is a nice intro to some of the theory behind it, very easy to follow.
It is a lisp, with visual similarities to clojure. Library access is irrelevant. The features that differentiate clojure are not there.
- Immutable and persistent data structures as the default
- Functional programming (no early returns or mutable bindings) as the default
- Reader literals for those data structures
- Concurrency primitives (including core.async)
- Protocols for polymorphism
From the hy docs: "Hy derives a lot from Clojure & Common Lisp, while always maintaining Python interoperability". Borrowing nice features where you find them is great, but it doesn't make it either a common lisp dialect or a clojure dialect. It just makes it a lisp with some similar stuff.
This is not a dialect of clojure, please fix the title.
But how recently have we developed the capability to:
- observe this thing at all
- accurately measure it's velocity and acceleration
- understand that it's velocity and acceleration were unusual?
Polymorphism doesn't require anything to do with OOP or objects themselves, see clojure multi methods as an extremely pure example that involves nothing even close to an object.
Protocols or typeclasses are also ways to implement functionality over (usually) immutable data. I don't see the relation to a mutable object with a closed set of methods defined at compile time.
a look at the related queries will show just how bad Google is at classifying searches for racket and scheme the languages as opposed to the words.
It's likely they're referring to the person's attractiveness as a potential candidate, not their physical appearance.
Or use a new name for the new interface whilst not breaking your old one. If your api is private then break it all you want, but if it's public and you want a large grateful user base then you should only grow. See rich hickeys talk "speculation" for a much better explanation of this.
Can't say I mind too much about subsidies for solar panels and electric vehicles regardless of the motivation.
I hear that slave labour and not worrying about workplace injuries really reduced budgets for the original.