HN user
One of my personal favorite channels for relaxation is this gaming channel:
https://www.youtube.com/@BinaryVigilante
I cannot believe how many good videos this (down to earth) guy has uploaded (1.1K) and for how long he has been doing it, yet still has hardly been noticed.
You clearly don't know what it means to be introvert. It's not a choice, it's almost like a phobia.
Before mobile phones where a thing, we used to memorize the phone numbers of every family member and friend and co-worker, etc. The numbers we rarely used, we wrote down or looked up in the phone book. When you got a new number, you maybe wrote it down, then after having dialed it a couple of times, it stuck. This didn't really require any effort, it was just the natural way of doing things.
Then came the mobile phone with the ability to store contacts, today I can't even remember my wife's number.
I have coded for more than 40 years and I hate autocomplete, language servers, etc. I don't use any of it because I have found (after having tried to use it all) that, just like with phone numbers, you don't remember much if you use all of that and you have to make a real effort, but things just don't stick the same way. But if don't use any of that, you only have to look things up in the beginning, then occasionally, then rarely or never again and more things just stick, you get faster in a natural way and you understand your code better. You also think deeper about how to structure your code and how to organize everything.
If you always use a crutch to help you walk, you will never walk by yourself. The crutch will look like it is helping you, but that's only in the beginning, eventually it will hinder you and hold you back.
That's my 2 cents.
I Made a Website for Problems
Nice. I already see a problem. It requires a Google account. I don't have a Google account and I do not want a Google account. So how do we solve that problem?
As far as I have understood, it's not something you can simply buy. Only certain industries get access to buying it.
I have a friend who works in production. I cannot remember exactly what his education is, but it's a type of engineer. If you want something produced that you have invented, he can get it done.
He has mentioned that they have software that can calculate the average lifespan of the finished product by entering the different components that goes into the product (like this piece has this amount of iron, this amount of tin, etc).
Based upon this the software can calculate the lifespan very precisely and determine if they have made it "too good". If it's too good the quality is decreased on purpose in order to reduce the lifespan such that people will buy more. Other testing goes into the equation as well, but enough data has been collected over the years that it can be calculated/simulated.
Thank you. Very useful comparison.
It's the same problem in Denmark as well.
Yes, let's have even more of people just writing code and not knowing anything about how anything works! Just what we need more of.
I hope you're joking here! If not, I would fire him on the spot. If for nothing else, he should not be messing with sshd debugging if he doesn't know what he is doing.
Exactly this! It's Sweden, not the US.
There is no sudden about it, SPA's are yet another one of the so-called "modern web" cancers of the Internet. They go completely against the protocols and architecture they run on and the only reason why they became so popular to begin with is because of all the hype from the big business, like so much else.
A web application or a website, by its very nature, is a series of small requests. When someone sends all requests in one big lump of a page, they have just defeated this very important architecture. Not to talk about the fact that they break searching on pages and a whole lot of other things.
Take a look at the Arch Linux wiki as a source of inspiration.
Exactly this! It's such a shame generics where added.
It's absolutely ridiculous in Denmark, how much "fat-free" is still provided in the shops and even the doctors still talk about it. This nonsense was rebuked long ago, yet they doesn't seem to know!
There is a major difference between the help you can get from an IDE or editor with a language server running in the background, and then GitHub Copilot stealing away other peoples code.
I sincerely hope Microsoft looses this law suit.
While we're at it, let's get rid of the chemicals. There is no situation in which the toxic chemicals doesn't create a whole new set of problems.
Here we go again, yet another wannabe code it like it's Ruby or Python. Frameworks are useless in Go!
No, it does not.
LibreSSL is not affected by this. It was forked before this vulnerability was introduced into OpenSSL, i.e. it's a new bug.
Can we not just dump OpenSSL for once and move over to LibreSSL already!?
Thank you for clarifying.
So, this is another "drive by" on Hacker News about Stripe, which @edwinwee (from Stripe) reacts to and "saves the day".
All the while the rest of us know absolutely nothing about what just happened!
What exactly is going on? What is the business model? And why does it require that these cases reach Hacker News before they are solved by @edwinwee!?
Infinite scroll is one of the several cancers of modern web development. It breaks the scroll bar, it ruins search on the page, the back button stops working, it's a pain for people with accessibility issues. Never use it!
Yeah, I was surprised at this. Maybe they will face out Dart too then.
You're missing the point. If you provide an API like in the example you give, put it out on the net at some domain, then in order for it to be REST, I MYST be able to access that domain, without any prior knowledge whatsoever, and make a request.
When I do that in the case you provide, I would not know anything about how to use those resources. Without any prior knowledge, I don't know what "users" are, or what a "like" is or an "unlike". In order for me to use this resource, I need documentation. Even if you provide the documentation in the response to the request, and I have to read that first, then it is NOT REST.
By the very nature of an API, it can never be REST.
No, that would not make it REST. I suspect you didn't read the article thoroughly?
If your application needs documentation, i.e. a spec or similar, also referred to by some as a "profile", in order for the client to use your resources beyond the initial root URI, then that is not REST!
An API, no matter how you twist or turn it, can never be REST. REST are truly only for manual human consumption, not machines. That is why it is so weird everyone is calling their APIs for REST.
We basically only use the Go standard library. So far we have found no use cases where that didn't cover us well enough.
This also removes any problems with third party dependencies that suddenly gets abandoned yet still have serious issues, supply chain attack problems, etc.
We have also found that most third party libraries tries to be (more or less) general purpose, so they often contain lots of stuff we would never need, so we prefer to e.g. write our own specific code.
The way we work require a little extra effort because we write the things we need our selves, but of course we reuse our HTTP handler code, our custom runtime error handler code, etc., from project to project, but in general the benefits far outweigh the cost in our experience. The fewer dependencies, the fewer problems - and Go shines in this because of how much is covered in the standard library.
Basically a normal HTML website, that's true REST.