Former COO and CIO of Hexagonal.
CEO of K-HOps.
Email: louis@k-hops.fr
- That's indeed a good example of prior full trusting of the browser by the server.
- I appreciate that, but in the case of TLS or CSRF tokens the server is not blindly trusting the browser in the way Sec-Fetch-Site makes it.
- This is a massive change for cache in webapp templates as it makes their rendering more stable and thus more cacheable.
A key component here is that we are trusting the user's browser to not be tampered with, as it is the browser that sets the Sec-Fetch-Site header and guarantees it has not been tampered with.
I wonder if that's a new thing ? Do we already rely on browsers being correct in their implementation for something equally fundamental ?
- This is my take as well. I've never come accross a JS project where the built-in datastructures were exclusively used.
One package for lists, one for sorting, and down the rabbit hole you go.
- As history showed us numerous times, it doesn't even have to be the best to win. It rarely is, really. See the most pervasive programming languages for that.
- Gitlab has had that for a while, and it's very useful as in-between through dot targets.
i.e:
.scoped-env: &scoped-env
Dot targets are ignored semantically, only inheritors make them useful.key1: value1 ...Then further down you can reuse *scoped-env wherever you need.
You can also have anchors on individual lines and compose them. It's useful.
The author suggests using ad-hoc syntax, or meta-keys. Gitlab supports that [1] and I use them as well.
Different but also combinable uses, for various people. Nothing wrong with it.
- There a lots of gamers. Games like Baldur's Gate & Expedition 33, which satisfies your criteria, far surpassed those numbers already.
I know people who rewatch the same TV series every year and go to the same vacation every year.
Fear of change is deep.
- I suspect it's a learning thing.
Which is a shame really because if you want something simple, learning Service, Ingress and Deployment is really not that hard and rewards years of benefits.
Plenty of PaaS who will run your cluster for cheap so you don't have to maintain it yourself, like OVH.
It really is an imaginary issue with terrible solutions.
- That is stretching the subject beyond reasonable. Proprietary software as a general endeavor is not an invalid business and nobody is saying that here.
LibreOffice is close enough to Microsoft's offering that surely it makes sense accross the many EU states to stop spending millions on it, and spend a few to close the gap, saving even more millions in the future.
- Chosing to pay millions when it is not necessary is definitely not a valid choice. It is at best stupidity, at worse corruption.
In my experience in the public sector in France, I have seen these decisions taken to advance someone's career.
For example, a first year free means a purchase person will get their promotion on incredible YoY progress.
- There's frequent discussions about how sonnet-3.5 is in the same ballpark or even outperforms sonnet-3.7 and 4.0, for example.
- Indeed, and with the technology plateau-ing, being 6-12 months late with less debt is just long term thinking.
Also, Europe being in the race is a big deal for consumers.
- Heavy user and I moved to Atuin because of the shell history scoping issue with regular bash history.
No matter my config it would always glitch. Atuin is backed by a global sqlite db: problem solved. And unlimited history.
I don't use sync though, commands sent to 3rd party servers are a no-go.
- I think the upside is that we stop spending limited human time on mundane/easy things and focus on higher-value pursuit.
Because you can no longer be a cheap artist, because you can no longer help students on easy problems en masse, because family businesses no longer need a webmaster.
That's a step in the right direction, maybe even towards UBI.
On growth, I disagree that we reached the plateau already. We won't fundamentally change things but larger context windows, speed, compute and cost? Obviously.
That in itself is a major evolution.
It looks like it is fading out of hype maybe, but that's just like all things. LLMs aren't going anywhere, just like Rails got version 8 out and it's better than ever.
- It's not allowed, but you'd have to sue if you uncover one such questionnaire, which is a hassle.
So instead, lying on your answer is not sue-able. Which makes including such questions ineffective.
- SEEKING WORK | Paris, France & OSlo, Norway | REMOTE
15 years of experience in tech, developing in all major paradigms, strong expertise in DevOps engineering, as a technical lead, a recruiter, good experience with CTO and COO positions.
I also work with another expert DevOps when my clients needs requires it.
- Do you want DevOps practices with a hands-on, pragmatic approach?
- Need realistic workflows for your developers to quicken release cycles, improve quality, tighten security?
- Wonder how to setup a technical team that delivers, from technology choices to recruiting the team, managing the tooling, and making that team time-resilient so you don't have to do it over and over again?
Let's talk!
Contact: louis@k-hops.fr
- I would honestly rather not make any user's Chrome experience better than Firefox given the curtent marketshares. It would not feel ethical to me to partake in helping Google seize more power on browsers.
- The big difference in my opinion is that your ad-hoc servers using static binaries, with all the outside stuff specific to your organization, are non-standard.
For some miraculous reason K8S is ubiquitous and everybody uses it. Standardization is a boon.
People complain about git using similar arguments, and yet having a vast majority of the tech world on it is a boon for tooling.
Both those technologies are excellent but take some time to master (you don't have to be an expert though).
I can get on a project using git, kubernetes and say RoR and understand it very quickly without help. It is well bounded. It takes a git account and a kubeconfig. All set.
A custom python codebase deployed on custom servers running in big enterprise-y network, not so much.
- It is statistically significantly harder to have a successful company as a solo founder. Having someone with a stake to bounce ideas and solutions off of makes a big difference. My associate and I regularly thank each other for catastrophes we avoided by our weekly night of talking over beer (and other daily exchanges).
I'm not too sure about _absolutely_ selling before making, but definitely do a market research and check if you can find people who would, at least theoretically, buy the product you intend to make.
If you make before you sell, you're saying that you are a visionary and people cannot understand your genius. Those are not odds to my liking, but if you like them you do you.
- Like I said in the last paragraph: I would not.
If the bash program evolves to span multiple files and lots of lines, I usually switch to ansible/ruby/clojure
- I am a bash expert.
This paper reads like it was written by clueless academics with no real world experience.
Multicore bash already exists and is seldom used, through the "parallel" cmd.
Other points address no particular issue, and would actually make the language more painful to use.
Bash has its limits, which pushes you to use a full fledged language if you attempt to walk past them. It's a good system.
- That would become unreadable in many cases, like du -sh *
- Same complaint here, I really like the project, hosted a server for a while, but ultimately the problems of verified users in channels were too much of a hassle.
To be fair, other E2E chat solutions have similar problems, like Signal. It feels more to me like we did not properly crack this problem yet.
I have yet to try it again but definitely want to.
- I disagree. Discussions about diversity and equality are absolutely political debate. It's even boringly trending I must say.
It's barely a 30seconds discussion between founders, not a company-wide debate. You follow it up with a yearly report on actual diversity vs real world distribution. That is, if you're big enough a company to be compared to it.
For example: if you have zero women in tech, there is a problem, and you have people to remove from recruiting roles. If you're close-ish to the median of your recruiting pool, you're fine. What need do you have for ceaseless internal discussions about it?
- Serverless is not so shiny when compared to a cloud-managed Kubernetes cluster.
I get to deploy stuff "the regular way", that is with a constantly running application, I don't have to re-train my developers, I have extra power in the cluster should I need it, I don't depend on a cloud provider in particular, and my costs are bounded.
Cherry on top: I don't maintain the infrastructure either, there isn't even a SSH daemon running.
- There is another problem, beyond the initial ads-based business. This information gathered about you, albeit anonymously, is correlated. This helps train models about groups of people, in order to derive value from group information. It can then be sold to insurances, banks, etc.
Derived information may look like: "Clojure programmers buy a new computer every 3 years on average" "Women in medium socio-economic groups tend to have kids at 31 years old"
But maybe I'm a programmer that cares about waste, and use the hell out of my computers, until it is completely unusable, making them last way longer. Maybe I'm a woman with trouble getting pregnant, and I won't have kids until much later.
Nevertheless, insurances and banks will use that information against me.
This information grouping you take part of, is de-humanizing. Humans are infinitely complex, ever-evolving creatures and categorizing us is profitable business. I do not want to be treated through the lens of the probability of a group I belong to, no matter how small the box.
- You can start off with an example you would find online, then use "kubectl explain" to read about the options used and other ones you want to use.
- Whenever I see video content I automatically think "I do not have time for this".
Text lets me efficiently skip through most of articles if they do not get to the point, or if they linger in ELI5.
The more I know about a field, the more I want to skip bits, because I don't need to be explained the basics over again.
- Decorators and AOP are very similar concepts in my opinion then, if you prefer.
I may add that investors are mostly US-centric, and so will the bubble-bursting chaos that ensues.