fraktl
The situation is not great, it's true that for regular users Chrome is basically spyware and battery drain.
I've been waiting for Mozilla to create a better webdev console (or even copy Chrome's) and I'd move instantly.
I do use more than just Chrome (ungoogled Chromium, Edge, Firefox) and I also experience the "regular user" problem when a site is fine in Chrome but not in Firefox so I'm split between two worlds as well, and believe me - I feel your frustration.
If you control domain.com and api.domain.com, then you can create a proxy that glues the two to the same domain, getting rid of any CORS annoyances forever. And you use the tech that exists. The whole problem takes less than 1 minute to type, test, deploy and there's no need for yet another big thing invented to solve a small problem that occurs due to ignorance of self-proclaimed "developers".
The simplicity is the hard part. Fishing for compliments by "pretending" it's so trivial to you shows immaturity.
The author definitely knows what he's talking about. Perhaps it's you who's doesn't?
> We started Quill with the goal of increasing the quality of human communication
We started Quill with hope someone buys us one day.
> Together with Twitter, we will continue to pursue our original goal — to make online communication more thoughtful, and more effective, for everyone.
We sold our data to Twitter so they can make more money.
> We’d like to thank everybody who has used Quill — if you came on board during our beta, or if you just sent your first message last week. We can’t wait to show you what we’ll be working on next.
We can't wait to use the data you supplied us for free to get even more money from Twatter.
This sounds like one of those people everyone on HN say to avoid in job environment.
No, it isn't security through obscurity. Yes, it protects and it protects a lot.
Thank you for contributing to lack of knowledge, do keep up.
But hey, with so many impostors around - they're not capable of fathoming how golden this advice is.
Sad truth is, since "developers" don't use this, they genuinely don't understand browsers and HTTP and that's what 's dangerous.
Just like you're endorsing being sponsored and effectively stealing GitHub's bandwith? :)
> We have a duty as practitioners in the industry to call it out when we see something wrong.
It's wrong both ways. You accepted the service from GitHub, the free one where you get to open your account, host your code, share it etc.
What exactly did you expect? To be served for free for your entire lifetime?
Please, get off the moral highground. You ate the devil fruit, now you're whining about it. You should be smart enough to know that this kind of whining will get you nowhere. Just quit.
Back then, there weren't bazillion web servers out there. A patchy server was still.. patchy. And engine that solves problem X (c10k) was not created yet :)
(for whoever reads my comment, I am referring to Apache and nginx)
It doesn't mean I hate people who work on ads / ad software. It doesn't mean I want to cancel them. You, and the others in that field, don't have to justify yourself. You don't have to donate to charity to feel better about what you're doing (it doesn't mean "stop donating NOW", it's just.. do what you feel is good, like you are doing now).
There's a lot of bad going on in the world. Ads are shady-grey area. I know how to fight it and have my internet ad-free. You're ok, don't let negative comments get to you. Cheers!
- You know how to use it (syntax, what it can do etc.) - You've learned its ecosystem, package management, standards - You can achieve results using PHP and complete projects while adhering to deadlines
Ruby doesn't offer anything substantial that would justify the switch. I'm all for developers honing their skills, but business does not exist to cater to developer's whims. Business exists to provide value to clients and put food on employee's table. Being nitpicky about the language and doing language swap is very expensive, especially when you swap language A with language B and gain literally nothing. For smaller businesses or one man shows, it's trivial to start a new project and use a different language.
I've seen fair share of superficial analysis and loud comments made by people who are not engineers, judging by their behavior. Like any language, PHP can be misused; and often is misused. It became a rite of passage to belittle PHP. Reading or hearing comments that attack certain technology without objective reasons merely means the person doing it is toxic and should be avoided in general. I dislike plenty of things in PHP / Python / Golang, but I would never dream of whining about it; instead, I try to reach out to maintainers and make suggestions to help make improvements.
Having written a few things, here's why you PHP is still appealing (this does not mean other languages cannot do this):
- it's sufficiently fast for CRUD-y applications. Bottleneck is usually I/O, but scaling horizontally is not an issue anymore, therefore performance doesn't have to be an issue. - it's feature rich, type system received massive improvements and continues to improve - it has more than 1 framework to choose from (Symfony, Laravel, CodeIgniter, Phalcon, Aphiria, Yii, Zend Framework and the list goes on) - there's an async framework available, called swoole. It's an extension to PHP written in C++ and it brings async capabilities to the play. It's sufficiently quick and allows for building different types of applications: like web socket server or communication-oriented servers. - new Foreign Functions Interface allows for experienced / polyglot developers to extend their apps in an easier manner opposed to writing extensions in C
With technologies like containerization, it became trivial to distribute PHP applications and avoid long setup times and reading the manuals on how to make something work. Not everyone use those technologies, but it's what's available and end result can be that you distribute a container image, which for all intents and purposes, means that you deal with a single "file" (thought I want to get across is that app distribution can be made extremely simple).
Question that poses itself is this: what reason is there to move away from PHP? Personal preference - I understand it, and this is what pushed me to try other languages and technologies out.
If you've got substantial performance, mature ecosystem, plenty of libraries, plenty of frameworks to choose from, great language features, async capabilities and ability to use the language for things other than CRUD-y applications - why use a different language that will ultimately merely let you do the same?
There's really no objective reason to use bitwarden_rs. Subjectively - we can do whatever we like, I'm not trying to challenge anyone into providing their reasons or into justifying their decisions, there's no right or wrong here.
They don't have your decryption key, therefore they save encrypted blobs and have no means to obtain your password. This takes care of trust issue - it simply is not an issue and never will be.
Even if malicious employee does something out of the ordinary or "hacker" gets the database, they still have the impossible task of breaking the encryption (which for all intents and purposes is impossible as of right now).
This returns us back to my starting point - there's *no objective* reason to use bitwarden_rs, apart from curiosity and/or convenience. I'm not saying it SHOULD not be used. We are all free to make choices as we see fit and don't need to justify them, however the reasons you listed are not reasons at all because the concerns you have don't exist.
Long story short - we use official Bitwarden and are paying for it and couldn't be happier. Bitwarden_RS looks like a cool toy, but I can't see any reason why anyone would run it. It's good for personal passwords, but Bitwarden itself offers free service so there's no need to venture down the self-hosted road.
I couldn't stop laughing, I miss stuff like this. Stavros - you are a god among mortal men, thank you for this :)
Don't get me wrong, but you don't seem interested in discussing, you rather appear to want to show how right you are without iota of PHP knowledge.
Since there's no dialogue here and you appear to be yet another code plumber, I'll bid you farewell and I wish you all the best in your career.
Honestly, after having used most of the languages at my disposal for past 22 years I've been doing this job - they were nothing special compared to PHP (or PHP compared to others).
You still have to figure the problem out before solving it with algorithms. No language or framework will help you do that.
I'm keen to hear why there are comments that demean one tool and elevate the other, when in reality - they're all just programming languages.