HNHacker News
TopNewBestAskShowJobs

kakwa_

1,465 karma · joined August 10, 2015

submissionscomments
kakwa_··on Open Source Thinkpad T420 Battery Design
Today, even older 10 years old laptops are quite good at doing usual things like checking emails, browsing the web, watching a video or doing things like that on the go.

Even coding is generally doable (unless your project is extremely massive).

It gets the job done, even if it's not as fast as recent laptop (which is in turn not as fast as a recent desktop).

Also, buying these things can make a lot of sense for some people.

For example, in my case, I'm a big fan of cheap laptop (usually secondhand thinkpad) + decent desktop.

On one hand a decent desktop is much faster than almost any laptops available (and the few laptops that are faster have issues like heat, low battery life and being heavy).

On the other, a small Thinkpad (ex: x250) is a good enough compromise when on the go. Also, as it's quite cheap (if secondhand), so it's not dramatic if it gets damaged which is always more likely for mobile objects. A few years back, I slipped on a patch of ice, felt on my old x61, and completely broke the screen, I just bought another x61 and swapped the disk and it only set me back 130 euros which not as bad as breaking a brand new macbook pro in the same manner for example.

So, yes, in the end, it's worthwhile to maintain them and do things like changing the battery or replacing faulty components. And the after market for this things is quite developed, you can pretty much find any components on ebay or other web sites (I just did it last week with a broken DC jack replacement on an x230). Combine with the fact these are some of the easiest laptops to disassemble, it makes them remarkably serviceable.

kakwa_··on Remington Arms Declares Bankruptcy
I'm far from an expert there, but most hunting riffles I've seen, at least here in France, shot shotgun ammunition (birdshots and the like).
kakwa_··on Remington Arms Declares Bankruptcy
Well, hunting riffles, even if there are extremely common in most countries, specially in rural areas, are hardly in the same class of weapon as a bolt action/(semi-)automatic riffle or an handgun. The latter also has a different goal in mind, being generally used for self protection/deterrence.

Also, carrying a gun all the time is extremely uncommon if not forbidden in most European countries if you don't have the proper permits. For example in France, IIRC, you can only get such permit if your professional activity justifies it (Police, Security Guards, etc).

Even for recreational/hunting uses you need to be registered, and maybe have a permit, depending on the type of gun. And that's just for ownership, it doesn't grant you the right to carry the weapon loaded and ready to fire.

kakwa_··on The worst tool for the job
Buying the cheapest tool can also easily discourage newcomers to a field.

As an example, I was nearly completely discourage from learning the guitar by the first guitar I bought. It was a really cheap stratocaster clone (<100$) with a really bad amp.

The thing was so bad that playing it was uncomfortable, and it was not even able to stay tuned thanks to the crappy machine heads.

Looking back, I would have been better off buying a decent guitar from the get go, something in the range of 200$ would have ensure that (brands like Ibanez or Cort are able to produce quite decent guitars in this price range, even Squier (Fender low price brand) could be decent enough).

The point is to at least invest a little, usually avoiding the absolute lower price items, but targeting items one level above.

kakwa_··on Does saying “Fuck You AWS” constitute offensive content?
Completely agree, Terraform doesn't abstract away the cloud specific bits, it pretty much exposes the raw resources.

Terraform is "multi provider" not "provider agnostic".

kakwa_··on Almost 1 in 3 pilots in Pakistan have fake licenses, aviation minister says
The Pakistani situation is actually not unique.

There are precedents, for example:

https://en.wikipedia.org/wiki/2008_Mexico_City_Learjet_crash

A Mexican government Learjet plane carrying the Secretary of the Interior crashed in Mexico city due to a mishandling of the landing approach by the pilots (they flew to close to a 767 and got blown away by wake turbulence).

The pilots were in fact not qualified, and in fact got fake licenses to operate the Learjet from corrupt flying schools.

> Pilot Martín Olíva and co-pilot Álvaro Sánchez, were not certified to operate the Learjet 45. The investigation concluded that both pilots had received fraudulent certifications: Captain Olíva lied about the number of training flights he had made, and had issues on the few training flights he did complete, while Captain Sánchez lied about being a Learjet 45 instructor. Both men had taken advantage of a corrupt system to get false training documents and some unsigned Learjet 45 certification forms from their flight schools. These revelations led Mexican authorities to suspend the licences of both flight schools.

kakwa_··on Playing around with the Fuchsia operating system
If I recall correctly, at the time, BSD was stuck in a lawsuit.

https://en.wikipedia.org/wiki/UNIX_System_Laboratories,_Inc.....

I'm wondering if it had a detrimental effect on adoption of *BSD, and thus increased Linux popularity at this early and critical time.

kakwa_··on Apple crushes one-man repair shop in Norway’s Supreme Court
There are abuses. But for cars, even with the insane markups, having car parts is still a win, specially compared to tech devices like iphones.

Also, cars are 1) a bit more complex 2) a bit more granular in design, which leads to more swappable components. This result in needing to replace just a few relatively small components in case of breakdowns (a pump, a filter, etc), and even with the markup, repair is often a good solution financially vs replacing the car. By contrast, on a phone, the individually swappable components are much bigger (a whole screen, a logic board, etc), making repairs less viable.

Last point is supplying spare parts is also quite complex logistically, which explains part of the markup. But not all of it, I agree, there has been numerous cases of price fixing/abuses, for example:

https://www.reuters.com/article/us-autos-software-pricing-in...

kakwa_··on Is a trillion dollars’ worth of programming lying on the ground?
From an European perspective, this has not exactly been my experience working with an international team.

The US collective mentality is sometime overly optimistic specially in public. This is sometimes a positive since it removes almost any inhibition regarding challenges, but it can lead to things blowing-up spectacularly, and then having to put in place hacks and brute force to make it kind of work relatively inefficiently and inelegantly.

But it also leads to great successes (biggest economy in the world, lots of major companies, very attractive country for talents) and innovations never seen before.

This positivism is prevalent in public statement but in private cracks start to appear. It gives me the impression that this positivism is pretty much a cultural obligation, so while not authoritarian, the group mentality is geared toward not talking to much about possible difficulties out of fear of being seen as too negative by the group.

kakwa_··on Personal income in the US shot up a record 10.5% in April
It is quite common where I live (France).

Personally, I've been working for ~9 years now, I worked for my first employer for a bit more than 5 years, my current job being the second job in my professional life. And I have a few friends still working for my first employer and who started there at roughly the same time as me. IIRC, my team leader actually started working for this company the same years I was born.

In my current job, I think I'm the only one in my team without the "5 years reward trophy".

At the same time, I've seen a few friends switching jobs every 2 to 3 years, but it tends to be more an early career thing and they settle after 2 or 3 jobs.

You have people who are jumping from job to job, but it's not the majority (at least for profession like Engineering, fields like Retail or Logistic is another matter).

kakwa_··on Oracle vs. PostgreSQL – A Comment
Vacuum is online, but with a caveat iirc, it locks the table with a lock that does not block inserts/updates/reads. But if your application use exclusive locks, things can get blocked.
kakwa_··on Oracle vs. PostgreSQL – A Comment
License cost tend to be negligeable compared to the cost of devs, dbas,sysadmins, etc, that's true.

But at the same time, it's a can be a huge speed bump in term of procurement. Waiting several weeks for accounting to accept the procurement of a license can really damage business or development speed.

It also adds significant admin load to track the license pool correctly and can represent a legal risk when inevitably, someone starts exceeding the terms of license (db size or db clones, or increase in hardware).

kakwa_··on But no, 80-column terminals in 2020 isn't “reasonable” any more
I would vote for something around ~100 with a tolerance for ~130 (CI/linter warning if between 100 and 130, maybe with a threshold limiting the proportion of lines per file in warning so that the tolerance is not abused).
kakwa_··on Why is Kubernetes getting so popular?
.rpm and .deb are geared more towards distributions needs. Distributions want to avoid multiplying the number of components for maintenance and security reasons. Bundling dependencies with apps is forbidden in most distribution policies for these reasons, and the tooling (debhelpers, rpm macros) actively discourage it.

It's great for distributions, but not so great for custom developments where dependencies can either be out of date or bleeding edge or a mix of the twos. For these, a bundling approach is often preferable, and docker provides a simple to understand and universal way to achieve that.

That's for the packaging part.

Then you have the 2 other parts: publishing and deployment.

For publishing, Docker was created from the get go with a registry, which makes things relatively easy to use and well integrated. By contrast, for rpm and deb, even if something analog exists (aptly, pulp, artifactory...) it much more some tools created over time which work on top of one another, giving a less smooth experience.

And then, you have the deployment part, and here, with traditional package managers, it difficult to delegate some installs (typically, the custom app develop in-house) to the developers without opening control over the rest of the system. With Kubernetes, developers gained this autonomy of deployment for the pieces of software under their responsability whilst still maintaining separation of concerns.

Docker and Kubernetes enabled cleaner boundaries, more in line with the realities of how things are operated for most mid to large scale services.

kakwa_··on OpenSSL 3.0
I've mixed opinions over the recent breakages I've witnessed in OpenSSL.

On one hand, I absolutely hate a library which breaks its API (I think lack of stability in interfaces is one of the bigger bane of the software industry and causes numerous issues down the line).

But in the specific case with OpenSSL, the breakages are legitimate imho. Most of the breakages I have seen are to clean-up interfaces and have a clear boundary between OpenSSL internals and items controlled by third party apps.

Concretely, they are switching from an API which exposed the internal structures directly to a getter/setter pattern.

Example in from one of my project:

old:

  ts_response->tst_info->serial
new:

  TS_TST_INFO_get_serial(TS_RESP_get_tst_info(ts_response))

Breaking APIs is always a balancing act, it's not something which must happen willy-nilly, but it's sometimes a necessary evil, and in the specific case of OpenSSL, if the project wants to go forward and improve in quality and stability, they are kind of forced to do it, it's just a bit regrettable that better design decisions had not be made from the start.
kakwa_··on EA will be releasing the C&C Tiberian Dawn and Red Alert source code under GPL3
I'm pretty sure it was only one CD. Keep in mind that the 600MB of CD was just huge at the time, so more than enough place for both versions.

At the time I had only an old 486 with a 500MB disk under DOS, and I played this game quite extensively.

I even remember cutting the sound to gain a few FPS, which enabled me to go from "unplayable" to "barely usable" ^^.

kakwa_··on Ask HN: I've been promoted to Architect. What do I need to learn/do to excel?
Moving from a DB engine to another, even if technically possible (right abstractions and everything), is often extremely painful once you have a few years of data.

(I'm currently involved in migrating quite a few large DBs, and it's a pain for everyone: SREs, support teams and the customers).

But yes, there is no "one size fits all", it depends pretty much on how your org is operating.

kakwa_··on Ask HN: I've been promoted to Architect. What do I need to learn/do to excel?
Architecture is also really useful in another regard: making the right (or at least "good enough") decisions on things that will be really painful to change later.

Think for example the choice of programing language or the DB technology used.

Architecture must strike the correct balance between vague guidelines and over-specification upfront. It should provide a framework which ensure homogeneity between components without restricting the teams/developers excessively.

On this subject, I found this presentation (by Stefan Tilkov): https://www.youtube.com/watch?v=PzEox3szeRc

Also, I'm currently reading "Designing Data-Intensive Applications", which is quite interesting and full of insight on the architecture trade-offs for data management and querying.

kakwa_··on Debian 10.4
Well, it's hardly a new issue.

Hardware support and lack of polishing has always been an issue in the Linux world and all distributions have suffered from it one way or another.

Having spent quite a lot of time in the past on this kind of issues, I do sympathize.

But from my experience, things actually tends to get a bit better now days, for example, I'm far less cautious about avoiding Broadcom ethernet and wifi cards as they generally tends to work out of the box today (even if I still prefer Intel for these).

Fighting hardware/default configuration issues is unfortunately be part of the game, but in my experience, it's a game I play less and less often.

kakwa_··on Debian 10.4
I've seen companies using Gentoo (with a lot of tooling around it) in specialized context.

Particularly in military contracts, Gentoo brings you several things:

1) you have a full audit trace from the compilation, and in paranoid situation, it's a huge plus.

2) it permits you to minimize the OS footprint quite a lot (feature flags), which helps improving security (less exposure).

3) it permits an high degree of customization, including the combination of software versions used.

4) it's relatively easy to import a patch and maintain an overlay yourself.

We have to keep in mind the constrains of Military contracts: The systems tends to be quite complex, validation is quite lengthy, updates are far in between, they tend to use specialized/weird/not powerful hardware which might need some tweaking, and the level of traceability is generally quite high.

kakwa_··on Rules of thumb for a 1x developer
This is indeed an incredibly dismissive view, only seeing the SRE as the poor soul you offload responsibility of things running well in production, despite the fact he is likely to have far less insight on what might go wrong and means to fix things.

Being basically in this position (but in a large follow-the-sun team, so I'm fortunate enough to not be paged at night), I can only underline the deep frustration such views can generate. Being paged every 10 minutes, being asked to fix things you have no control over, getting answers like "what? the server is overloaded? it's an infrastructure issue, not a bug in our code" and seeing developers cry when they get a ticket a day, when at the same time each SREs in the team is receiving a dozen, it can lead to some resentment.

A saner approach is to have the SRE as the first line to filter bugs/alerts/tickets out, but being able to call a developer if required. The SRE can also be an active team member with more insight on production constrains and pain points and maybe system architecture recommendations for the whole team. Also, in my opinion, developers should be an active part of running things in production, otherwise the whole dev team can lose touch with reality and lose sight on how well or not things are actually running.

kakwa_··on New Air Force One instruction manuals cost $84M
Also, it must not be forgotten that there is a lot more than writing the pages themselves.

On a document this big, you need to properly organize and index it so that the maintenance personnel would be able to find the relevant bits easily. that's a lot of editing job required, and a lot of coordination (to properly reference and label each subsystem for example).

Also, this document requires a lot of reviews and a lot of the maintenance procedures needs to actually be performed to actually check if they are clear enough to be executed reliably by operators/maintenance personnel.

All that is a lot of work, requiring a significant amount of man hours by skilled people and hardware and tooling available for validation.

kakwa_··on Team Fortress 2 source code has leaked
Developing an Open Source software can have some incentives to have cleaner code.

Talking from personal experience. Here are my though on it:

First, with Open Source software, you expose (potentially) what you write to the while world, as a consequence, you don't want to feel ridiculous by publishing atrociously bad code. In contrast, in a corporate environment, the code is not seen by so many eyes if at all, and even if read, the readers are roughly a known quantity.

Second, You have far more time/freedom, specially if it's a personal project, to think about design/code architecture, and to rework things if required. You can also spend time on things like unit tests, fuzzing, etc. Basically, you can more easily work on all these things that are "valuable" but difficult to "quantify/measure".

Third, people working on OSS projects are generally a bit more motivated, either because it's their subject of interest, or because of the general appeal of OSS.

Forth, often with OSS, you actually have more resources/service available to help with code quality. CI, static analysis, dependency auditing, etc is one click/integration away. In a Corporate environment, the procurement for such services can be off-putting, integration setup can be an up-hill battle, and there can be strong restrictions regarding external services.

Just as an example, in a previous job, I tried to get budget for a Jenkins server, never got it, so I ended-up "stealing" an old abandoned server from another project, once I got it I ran into issues not being able to configure the post commit hooks to trigger a CI build. Heck, in this job, even my home desktop was a 3 or 4 times better development machine than my work laptop.

Things are changing slowly, having a good code coverage is more and more a goal if not a company policy, code review processes are more and more common, companies are a bit less paranoid about trusting external services for CI/analysis/fuzzing. But from what I have been able to see in most of my job, proprietary code bases tend to be lower quality than most OSS projects. Even the code I've produced in my free time tend to be better than the code I've written at my job.

It's not an absolute however, you can still have terrible OSS code bases, it's just you are a bit more geared towards better code quality in OSS projects.

kakwa_··on OpenSSL high-severity bug – affects 1.1.1d, 1.1.1e, 1.1.1f
Also stability of APIs/ABIs: within a major Ubuntu/Debian version, there is an implicit contract in most cases that if you build something against a library/software provided by the distribution, it will not break after an upgrade of said library/software.

To enforce that, a policy of version freeze+backport of bug/security fixes is almost always necessary as very few upstream projects will maintain separate branches and have a clear policy about API/ABI breakages.

(OpenSSL is actually somewhat of an exception in that regard).

kakwa_··on Codeberg: a free, non-commercial GitHub alternative
It's not the case, the PRs, bug tracking and other metadata are stored inside an SQL database:

Here are the tables on my at home deployment:

  mysql> show tables
      -> ;
  +---------------------------+
  | Tables_in_gogs            |
  +---------------------------+
  | action                    |
  | attachment                |
  | collaboration             |
  | comment                   |
  | commit_status             |
  | deleted_branch            |
  | issue                     |
  | issue_assignees           |
  | issue_user                |
  | milestone                 |
  | mirror                    |
  | notice                    |
  | notification              |
  | oauth2_application        |
  | org_user                  |
  | protect_branch            |
  | public_key                |
  | pull_request              |
  | release                   |
  | repo_indexer_status       |
  | repository                |
  | review                    |
  | star                      |
  | stopwatch                 |
  | task                      |
  | team                      |
  | topic                     |
  | tracked_time              |
  | update_task               |
  | upload                    |
  | user                      |
  | watch                     |
  | webhook                   |
  | [...]                     |
  +---------------------------+
  67 rows in set (0.01 sec)
Edit: delete a few lines in the list of tables, it was way too long for an HN post...
kakwa_··on Codeberg: a free, non-commercial GitHub alternative
Personally, I kind of like the balance of gogs/gitea on that subject.

You can switch language quite easily using the menu in the bottom center/right.

Also, in a self hosted context you can disable/enable languages in the configuration file easily.

Also, if you find the translation really bad (I think in most cases, the default translation is from MS automatic translation), you cam easily contribute to it:

-> https://crowdin.com/project/gitea

I personally contributed to the French translation a few years ago, which was really bad in Gogs at the time, specially with some over translation of technical terms such as "git commit" which was translated to "git commission" (a bit weird and laughable since "faire une commission" can be a weird formal way to say "pooping" in some contexts).

I took me a few hours to go through a few of the message strings and propose an hopefully better translation. It's quite easy to contribute to the project in this manner, far easier than contributing code.

Lastly keep in mind that gogs was created by a Chinese developer, and I'm half expecting that Chinese developers are not as fluent in English as developers from India or Europe. In this context, pushing for an internationalized service is a good call vs an English only UI.

kakwa_··on Configs suck? Try a real programming language
I'm not sure why choosing a configuration file format like ini or yaml prevent configuration validation. This logic can be expressed within the program itself: parse the file, and validate inside the program that the configuration is consistent.

Also putting the validation logic directly inside the configuration file is not a good idea in my opinion for two main reasons:

* the validation logic is then "external" to the program and can be overridden (with potential catastrophic effects) by the operator installing the program.

* Configuration validation logic can be quite complex, and having it inside the configuration file would clutter it too much in many cases.

I tend to see configuration files as an API/Interface (maybe because I'm an SRE), and as any interface, I want it clearly defined, with known boundaries and as explicit as possible. For these reasons I'm not a big fan of using a fully fledge programing language as configuration.

kakwa_··on Configs suck? Try a real programming language
CI systems tends to be more about defining a workflow than setting simple parameters, specially if they also handle CD.

For that reason, something looking more like a programing language feels more appropriate to me.

I kind of like the Jenkinsfile syntax for this use case as a CI workflow is not a static definition defined by a configuration file (yaml, json or ini) but the syntax is also not a fully "open" programing language like Python which would authorize too many potential hacks.

A specialized DSL in this case seems more appropriate and being the correct balance between flexibility and complexity, at least for most needs.

kakwa_··on OpenTTD 1.10
Yes, iirc, towards the end of Capital in the 21th century, he takes universities investment funds as an example (as they can quite large and data is public). And there is a strong correlation between the size of the fund and it's return.
kakwa_··on How to manage HTML DOM with vanilla JavaScript only?
If you don't refactor and update your dependencies regularly you can easily end-up in a corner.

You can be hit by a bug in your dependencies, be it a functional one or a security one, but if your dependencies are completely out of date and there is tons of API incompatibilities between the version you are using, and the version implementing the bug fix, it will be really painful and take a long time to update, with stakeholders breathing down your neck expecting a fix asap.

Also, maintaining old tool chains can be a real drag (maintaining older building hosts, developer machines or VMs).

Updating frequently to be near enough the latest version is generally preferable.

← PreviousPage 7 of 19Next →