1. They appear to be more expensive than consumer TV’s
2. They might be more difficult to find through usual channels because they are targeted at businesses (but it probably depends on where you are located)
1,577 karma · joined May 15, 2019
1. They appear to be more expensive than consumer TV’s
2. They might be more difficult to find through usual channels because they are targeted at businesses (but it probably depends on where you are located)
Second, I am not sure what is a bigger joke here, the project itself and the OP's innocuous and cute self-promotion or the fact that this post landed the HN's front page.
0. Terms and definitions.
"You" refers not to the author of the tool but to the dear reader who happens to stumble upon this comment in the stream of random screen scrolling.
1. Comment body.
Couple of things about CS classes and specifically about programming classes. They will teach you everything but the most important engineering principles. And you'll have to adjust your learnings once you leave the campus gate behind and enter the wilderness of real tasks and challenges.
The first biggest lesson I learnt as a CS graduate was that the most beautiful, efficient and valuable software program is the one that does not exist, literally no code[0]
The second biggest lesson I learnt as a CS graduate was YAGNI[0]. You never ever write a single line of code, even touch the keyboard until you are absolutely sure you have exhausted all possible options to solve your problem without getting your hands dirty with programming.
The third biggest lesson I learnt as a CS graduate was RTFM[2]. It is so exciting to go to conferences and see people present fancy slides and watch youtube videos with lollipop coloured pictures explaining some complex topics in a eli5 style. Or read blog posts on a gazillion of websites posted by unknown unknowns but yet coming so convincing as if they were written by John Carmack or ChatGPT 5. But then none of them tell you the whole truth and show you the full picture. It is only official documentation, manuals and boring reference specifications that can help you find what you are looking for. And you will need to learn the skill of grinding hunderds of pages of badly styled refdocs to find that really nitty gritty quirky feature that consumed your whole day in finding out why your code does not work as expected. That's where you will start proceeding to the official docs and source code (if needed) before anything else (even Stackoverflow!).
There have been so many git wrappers around, you can probably try them all (tig, jj, gh-cli, gitui, lazygit, gix, you google it). But then, no matter how much effort their authors invest in those tools, there will always be inconsistency between git and its wrapper and you find yourself resorting to git to do what was supposed to be covered by the bespoke tool. And then you learn to respect git, understand its concepts as they were designed, learn some bash and git aliases[3], ditch all those tools (or the majority of them) and proceed with your personal tailored toolbox where if you find something odd you adjust it for your needs within 10 minutes and chill out.
[0] - https://github.com/kelseyhightower/nocode
[1] - https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it
The only recommendation to everyone: move away or duplicate.
One of the strategies I am yet to test is the synchronization between gitlab and github for protected branches and tags and relying on their container registries. Thus (at least) you provide multiple ways to serve public images for free and with relatively low hassle.
And then for open source projects’ maintainers: provide a one command way to reproducibly build images from scratch to serve them from wherever users want. In production I don’t want to depend on public registries at all and if anything I must be able to build images on my own and expect them to be the same as their publicly built counterparts. Mirroring images is the primary way, reproducing is the fallback option and also helps to verify the integrity.
Apple should close this gap and I am puzzled why they have not done that yet. Because even for iOS development people need things beyond the xcode toolcahin and they resort to either of the available options. Homebrew is just one of them.
Not only cli app store but the mac app store also badly needs some love.
JSON (as per spec) is a lightweight data-interchange format.
YAML is a "human-friendly data serialization language for all programming languages" and by mere coincidence (it does not look to be by design until version 1.2.2 [0]) JSON is its subset and not vice versa!
And YAML is human-friendly in two ways:
- it is notoriously "human" in interpreting input, i.e. ignoring the context or misinterpreting others' words;
- it helps read serialized data via indentation-based syntax.
The biggest caveat is for whatever reason everyone ignores the key highlights of both JSON and YAML that are "data-interchange format" and "data serialization language". If I were to interpret these two terms I would rather say they both present great means for heterogenous programs to exchange data with YAML being a fancier brother better suited for human eyes. They were not meant to be used for configuration purposes or what not. But people started using them exactly for this purpose instead of creating a configuration format/language that would render into program-readable JSON(if needed).
CUE and Dhall are perhaps the first two attempts to create specifically a configuration language with the ability to serialize in yaml/json/etc.
I very much hope using YAML, JSON and even TOML for writing configurations will become an anti-pattern soon and will be replaced by something more suited for this role.
Remember:
- you pay once for a single item - you own.
- you pay on a regular basis to access multiple items - you don’t.
As simple as that. The pre-internet model is a book library. You pay a small monthly fee for the right to borrow books subject to some rules and limitations. You don't own them but on the other hand you have access to a huge collection of resources owned by someone else.
Same story with all the music and video streaming services. Someone owns a huge collection of media and you can buy access to this collection if you pay a relatively small regular fee.
If you really want to own stuff then you need to invest a substantial amount of time and money into organizing your own library or collection of music, video, books or whatever else you are passionate about.
Not sure if this convention is actually documented anywhere.
Random examples:
- https://github.com/PyCQA/isort/blob/main/pyproject.toml#L100
- https://github.com/pypa/pip/blob/main/setup.py#L78
- https://github.com/11ty/eleventy/blob/master/package.json#L1...
There are several major problems with Signal:
- it is not that private after all since it requires a phone number. Yes, you can override this by using some virtual throwaway number if you are geeky enough but your account will be associated with this phone number anyways.
- as a consequence you _will_ receive spam from bots fanning out messages to phone numbers. You can’t restrict your social circle to allow only chosen people or let’s say people only from your contact list to message you.
- Signal protocol is probably great from the e2ee perspective but it is not federated and unlike XMPP you cannot spin up your own server and have full control over it.
- Since the end product is not a protocol or a framework or a platform it is a product that is run by other people who you can only trust albeit you can verify and audit source code by yourself(or by hiring someone to do it on your behalf). And I am sure you cannot run an end-to-end audit of the whole Signal platform to verify that what they actually run has been built from the source code you have audited.
- Since it is centralized, Signal is prone to censorship in those countries that decide to fight it. This leads to introducing workarounds like this https://signal.org/blog/run-a-proxy/ to help people circumvent limitations in affected regions and territories.
Time. Time. What is time? Swiss manufacture it. French hoard it. Italians squander it. Americans say it is money. Hindus say it does not exist. Do you know what I say? I say time is a crook.
Car manufacturers have been into planned obsolescence for a long while and now they want to continuously charge me for their crap.
Vote with your wallet!
“Gross”: #7EC170
Real from the bottom of the message reel: #65C466
Real from the top: #73E173
No issues with contrast in either case. Also keep in mind that those color hexes will slightly vary depending on where exactly you decide to pick since bubbles are filled with gradients.
Not sure where author gets his bubble from but in real life they look as “good” bubbles at the bottom of the screen that makes me think the article itself is gross.
13 months, 28 days each. Year day in the end not belonging to any month, leap day every leap year in the middle of the summer.
https://en.m.wikipedia.org/wiki/International_Fixed_Calendar
I want everyone to use UTC and align local lunch times to solar noons.
"Everyone hates YAML. Everyone writes a lot of YAML."
Duplicate your efforts and do not rely on a single git hosting provider! Gitlab.org is there. Use it. There are multiple ways to sync workflows and git repositories
This! I have come to the same conclusion. If you want to construct a building you have to comply with multiple standards and industry regulations that serve as limitations and safeguards that follow your project from the initial idea up to (sometimes) the point of destruction of the constructed object.
In our industry even with the standards that we have they are oftentimes treated as guidelines not rules. Of course there are exceptions but those are just a byproduct(or proof) of the rules themselves.
There are a couple of strategies one could rely on to mitigate the risk of github downtime:
- create a map of features between github and competitors, find the common denominator and risk accept anything that is unique to github but viral for your business/product;
- maintain a primary self hosted instance of gitea/gitlab/sourcehut and use github as a mirror; - use github as a primary platform, maintain mirror with public gitlab and switch to gitlab in case of outage;
- if github is used beyond its primary purpose(git hosting) put some efforts to maintain the same features in gitlab/gitea/sourcehut, i.e. use CI features of both platoforms and push releases and artifacts to both of them so that end users have the choice.
- separate concerns and not go all in with github as a platform for the whole SDLC and project management and instead use different tools/platforms for different purposes.
Yes, it takes more time for the initial setup but it quickly pays back.
The above applies to those cases where your products need to be hosted publicly.
71% welcomes all sorts of isolation, sanctions. They don’t care if tomorrow all western companies shut down business in Russia. “Iran has coped, so do we”.
All currently imposed sanctions hurt neither Putin nor his “electoral base”.
Around 20% of the population in Russia are intelligent and educated people who don’t support that shit. Just because it is absolute bonkers to invade another country.
Those 20-25% are badly beaten by sanctions. And they are fleeing Russia, or trying to restructure their businesses and lives in the new distopian reality.
The majority of what is being imposed on Russia right now affects the vulnerable middle class in Russia. And they have two options: immigrate or (if immigration is not an option) shut their mouth and deal with the orwellian reality.
As an end user I would be sure that my data is encrypted in-transit and at rest.
As a cloud provider I would take care of encryption and privacy promises and transparency and care about my bandwidth and storage costs.
Risks:
- bad cryptography/leaked keys. Mitigation: sound cryptography, open source model of development.
- all possible attacks from the public about potential usage of the service for CP, terrorism and other deadly crimes.
- the rest of the risks that apply to e2ee messaging as well.
// just off the top thoughts
1. Get a technology proven to have solved a given problem more than 100 years ago.
2. Throw ICs on top of it.
3. Put “smart” into marketing materials.
4. …
5. Profit
There is nothing in any dishwasher[0], fridge, vacuum cleaner, washing machine, ${you_name_the_home_appliance} that would require to be smarter than they are without those (actually far from smart) hardware and software that is being installed and imposed on customers. If combined with the planned obsolescence[1] it creates a perfect combo.
Check here: https://github.com/ibraheemdev/modern-unix
Some of them are great, some are opinionated.
I believe the actual technique should be like “break 5 layers of your confidence in a given problem and _question_ everything about it until you build the whole picture”.
In other words instead of asking why 5 times question everything and unwind the knot until you have a straight thread. Sometimes it is not just 5 layers deep.
And one should be brave enough to put their own beliefs and experience under doubt and reassess them from the ground up.
That’s the path that leads to some really interesting questions about yourself, the world around, about other people. That’s what ignites the thought process.
5 whys is an oversimplification of the actual reasoning process. And as with other ideas that get wrapped up in a fancy proverbial form it can be misleading and turns to a cargo cult.
Start with “why should I trust the 5 whys? Will it really lead me to right answers? How? What if the answer is no?”
There has always been all kinds of drama, addiction, obsession, love and hatred.
But I can’t stop thinking that modern websites just monetize by growing the userbase. This model kills creativity and we are juste cattle for them to feed us with some bullshit.
And some random guy nowadays instead of registering a domain name and creating a bunch of html pages to share his thoughts and observations no matter how weird and awkward or enlightening they are, just a small comfort zone in the neverending blizzard of data traffic - this guy will go create a facebook/instagram/youtube/etc. page, get all sorts of rage and ignorance, get kicked by violating some stupid ToC rule of the bespoke “social” “media”.
Long gone the times when internet was a place where you could stumble upon something really touching.
There are nice places to visit but google favors to show crap on its first couple of search results pages nowadays
* Well, by “we” I mean to say people born before 1990 probably
MS Windows is Heaven on earth in this regard.
In the sense that whenever there’s a new API or service available in any of public clouds and their official SDKs there will always be a delay before this new service/feature/API will become available in terraform.
First time I encountered it with GKE private clusters 3 or 4 years ago. Now it is AWS Keyspaces.
The second biggest reason is whenever you have a requirement for a hybrid or multicloud then well you are left with rigidity if HCL. It is probably doable but for what sake?
Solution: get a real language, write a STATELESS configuration management(IaC) system for your own needs and maintain it. The majority of public and private cloud providers ship SDKs in most popular languages that will help you build your own software solution and reduce your dependence on a third party which I would put under progressing operational risk category. Yaml/json/cue/toml for end user configs would suffice.
Example: for one of my previous projects were built a tool for a hybrid AWS-openstack setup, and were managing a dozen of busy environments.
It has proven multiple times that privacy and security are not something they really care about.
I wonder what else should happen for everyone to completely lose trust in this scam.
The next step will be a popup saying “this tweet is available in the official app”