Here’s the exact line from your license file:
Change Date:2023-06-29 2027-01-01
Seems like it should really be interpreted to mean the Apache license started applying on June 29, 2023.
2,699 karma · joined March 20, 2013
Change Date:2023-06-29 2027-01-01
Seems like it should really be interpreted to mean the Apache license started applying on June 29, 2023.
To complete the metaphor: “I will only eat meat on Wednesdays for the next four years, after which I will be 100% vegetarian.”
As someone who is annoyed anytime proprietary-licensed software tries to capitalize on FOSS terminology, I concede that being immediately source-available with a guarantee of being OSS within a reasonable timeframe is still better than we’re likely to get from the majority of projects.
Voting and UBI are often cited as valuable use cases.
It will definitely be subverted if it becomes widespread enough to be impactful.
They should update the main readme to include this under Features, and also call it out in the demo files.
Digger makes it sound like it might address this:
> Digger runs terraform natively in your CI. This is: Secure, because cloud access secrets aren't shared with a third-party
From the Github+AWS demo:
> 4. Add environment variables into your Github Action Secrets (cloud keys are a requirement since digger needs to connect to your account for coordinating locks) AWS_ACCESS_KEY_ID & AWS_SECRET_ACCESS_KEY
It sure looks like AWS admin credentials are shared with Github, and also available to anything else in the diggerhq/digger action.
Also, what this person said :) https://news.ycombinator.com/item?id=36552245
I use the app exclusively for identification, but it feels like there’s so much untapped potential, which you summarized very well.
I’m glad to have a vigorous discussion about code I wrote during my own time. Go ahead and create a standard rubric that covers the project itself and the follow-up discussion. This is what I’ve done when hiring. It’s great because it demonstrates the employer knows what they’re looking for from the role, and that the team has sufficient experience to conduct a conversation in the relevant domains.
When I hear there’s a minimal number of interviews, and the main one is an intense live leetcoding session, I tell them I have no interest but if anything changes on their end I’ll be glad to provide sample work and have a discussion about it. The problem is these live sessions are extremely draining to prep for, provide no gain for the candidate (unlike writing code that can be retained), and they reveal practically nothing about the company.
I’m not sure if lsat.tech is having issues, looks like the protocol was recently renamed L402: https://docs.lightning.engineering/the-lightning-network/l40...
echo test > /dev/tcp/<ip>/<port>
Both are tools for defining kubernetes manifests (which are YAML) in a reusable manner.
Jsonnet is a formally specified extension of JSON. It’s essentially a functional programming language (w/some object oriented features) that generates config files in JSON/YAML/etc, so it’s straightforward to determine whether an input file is valid, and to throw an error that points to an exact line if it’s not. It has a high learning curve, especially for people whose only experience is with imperative languages.
Helm charts also generate YAML/JSON config files, but they use Go templating. This is easier and faster to understand, since it’s mostly string substitution and not much logic (there’s conditionals, iterators, and very basic helper functions). Unfortunately a simple typo or mistake can cause errors that are difficult to diagnose (the message may indicate a problem far away in code from the actual mistake). It can also generate output that’s valid according to the string templating rules, but not what was intended, which can be very confusing to debug.
Despite these shortcomings, the vast majority of kubernetes applications are distributed as helm charts. I understand why things ended up this way, but I still wish it were more common for people to invest the upfront effort to learn the superior tool, so it could be more widespread.
Edit: and the Quest 2 will be reduced to $300 in a couple days from now
It’s not about the kubernetes package manager, for anyone wondering.
> By design, the Bitcoin protocol has a low throughput. The Lightning Network (LN) is a layer-two solution built to increase throughput by cryptographically securing commitments to transactions and only occasionally converting cumulative balances into on-chain transactions. LN channels enable payments between nodes connected by a path of channels. The payment flow through a channel determines its cost. Different channel topologies can support the same underlying flows, but impose different costs. This paper obtains necessary conditions for cost-minimizing topologies by identifying local cost reducing strategies: The first local strategy entails repositioning of channels. The second entails adding hubs to handle the flows of group of nodes. The paper also evaluates the efficiency of a global configuration, obtaining bounds on the cost of the cost-minimizing topology and showing the unusual circumstances in which the cost minimal structure is a hub that connects to all other nodes.
The headline seems misleading, like it’s for a single month.
> Print copies, wherever they are bought, come with free electronic versions in PDF, ePub and Kindle formats. With your print copy in hand, register it on the Manning site and you can download the digital versions from your account.
No affiliation, I’m just a long-time satisfied customer.
They also sell their eBooks as normal PDFs (no DRM).
I assume it’s a healthy combination of making high quality technical publications easy to acquire at a reasonable price. Similar to how digital movie and music piracy finally died down when that media became reasonably easy to acquire legally.