I would argue that the barrier to entry is on par with python for a person with no experience, but you need much more time with Haskell to become proficient in it. In python, on the other hand, you can learn the basics and these will get you pretty far
I think smalltalks just didn't bring you to the right topic, if you were to reach topic you both fancy, you would definitely remember each other. If anything, having a smalltalk is nicer than staying in awkward silence.
Unless there is some vulnerability in the current version that you want to take advantage of. See e.g. mediatek exploit to unlock bootloaders without authorization by OEM or hacking PS4.
While I don't use GitHub for personal projects, I don't see how moving off GitHub solves anything. If you are open source contributor, then repositories you interact with are public, and there is nothing preventing anybody (including GitHub) from using your code for any purpose. If you contribute to a public repository on any public platform, be it Codeberg, sourcehut or GitLab, your activity is public, issue you create are public[1], everybody knows who changed what in the code.
The social media effects are twofold, on one hand I think stars and contributors count, contributor profiles are great to see what is popular, but it went a little too far when they added scrollable home page. Virtually everyone has an account on GitHub, the best way to make your project visible and ease the contribution threshold is to put your project on GitHub.
What I would like to see is federated git, so that some protocol allowed different git servers could communicate with each other, which will make moving off GitHub much easier.
[1]: except for sourcehut I guess, which does not have issues or pull requests?
As a younger person myself, this talk is incredibly entertaining, kind of eye-opening too; the passion for engineering that speaker radiates is immeasurable.
For me lenses are like water. I start each haskell project with `optics` dependency, my favorite trick is deriving Generic and using labels to access the fields[1]. Field accessors never get created in the first place, so you have no namespace pollution and all your data definitions can have fields called `id`, `date`, whatever and never collide with each other or imports from other modules. The only problem is unwieldy error messages in case something goes wrong. Another tool is Magnify and Zoom[2] classes, which are useful for limiting context available to child actions in a monad stack. You can have one "global" state, but give only a slice of that global state to the child action with `magnify #subState1 (myAction1 arg1 arg2)` (or zoom respectively for MonadState actions). This approach is extensively used within Brick[3] TUI library, where you have big "global" app state, and a collection of widgets that have their separate states which you slice from the big state.
Good information, but you can already turn this off via the (quite hidden, I admit) setting that is mentioned in the article. That's a better way to turn this off completely, rather than patch it via a visual rule.
Brave browser does not have an option to turn it off but uBlock Origin custom filter works.
In the Brave community the only solution offered was an adblock filter:
brave://adblock (custom filter) ||accounts.google.com/gsi/client$script,third-party
Either way it's something you'd need to go out of your way to configure any time you interact with a new web browser. And both ways can be disabled randomly (Chrome settings changes during browser updates, or uBlock extension being deprecated).
I had a similar problem where I can't remember the answer to the card, but after revealing it, it seemed too easy to make it due in a few days, so I would lie to the program and press Hard/Good. Later I removed scheduling times on top of buttons and decided to trust the algorithm. I believe it helped me to stop caring about schedule times and loosing progress on a certain card. After all, these algorithms were made for ordinary people with ordinary memory behavior.
I think my problem is that I'm not using the system as intended. I learn new vocabulary mainly by reading texts or watching videos in the target language and use spaced repetition to keep track of my progress. If I can't remember a word (as indicated by SR), I'll reread the text/rewatch the video where I've first encountered it. I don't want to keep reviewing the same word in my spaced repetition program, especially not in the same session.
reply