I'm also the author and maintainer of an authorization service for Heroku web applications: https://elements.heroku.com/addons/wwwhisper
You can contact me at jan@mixedbit.org
- mixedbitI think the argument is that the building was able to generate such income stream, in this case the stream comes from the owner. The owner is betting the investment will pay-off at some point, so is taking temporary loses (you could say that the owner is paying the rent for the vacant places).
- Missing: Tesla to release full unsupervised self-driving mode in 6 months
- An interesting things is that GitHub is an expensive service and my guess would be that MS makes good money on it. Our small company paid about 200+ USD monthly for GitHub, much larger cumulative cost than Windows licenses. My believe was that Windows is getting worse, because it is considered legacy business by MS in favor of new offerings such as GitHub subscriptions.
- This is architectural problem, the LUA bug, the longer global outage last week, a long list of earlier such outages only uncover the problem with architecture underneath. The original, distributed, decentralized web architecture with heterogeneous endpoints managed by myriad of organisations is much more resistant to this kind of global outages. Homogeneous systems like Cloudflare will continue to cause global outages. Rust won't help, people will always make mistakes, also in Rust. Robust architecture addresses this by not allowing a single mistake to bring down myriad of unrelated services at once.
- Do you honestly believe there are people on this board who haven't used LLMs? Ridiculing someone you disagree with is a poor way to make an argument.
- Before LLMs programmers had pretty good intuition what GPL license allowed for. It is of course clear that you cannot release a closed source program with GPL code integrated into it. I think it was also quite clear, that you cannot legally incorporate GPL code into such a program, by making changes here and there, renaming some stuff, and moving things around, but this is pretty much what LLMs are doing. When humans do it intentionally, it is violation of the license, when it is automated and done on a huge scale, is it really fair use?
- With self driving cars population on roads increasing, a side effect can be that all traffic will be shaped towards staying within the speed limits. With more cars staying within the limits, breaking the limits becomes more difficult.
- For containers you will also have own TCP/IP stack similarly to what is shown for VM on the diagram, this is done when a container uses slirp4netns to provide networking. An alternative is to use kernel TCP/IP stack, this is done when pasta is used for networking, diagram on this page shows the details:https://passt.top/passt/about/.
- As Stuxnet showed us, you don't need to run a nuclear program to be infected by malware developed by state level actors.
- I wonder how practical it would be to build a system that would let home appliances cheaply overuse energy when there is a peak in wind or solar production. For example:
* Let heat-pumps heat homes to say 23C instead of 20C
* Let freezers decrease the temperature to say -30C instead of -18C
* Let electric water heaters heat water to say 70C instead of 50C, such water can then be mixed with more cold water
Such overuse would then reduce energy consumption when the production peak is over (heat pumps could stop working for some time until the temperature decreases from 23 to 20, etc.)
- With phone hardware lifetime so short, would it be possible to catch-up with hardware update cycle? I guess each new version of a phone can ship with new versions of binary blob drivers. As mentioned in the announcement, reverse engineering the blobs is a huge effort, when it is done, hardware may already be out of sale and the effort would need to be repeated for new versions.
- Depending on your system, passing secrets via environment can be more secure than passing secrets via a command line. Command line arguments of all running processes can be visible to other users of the system, environment variables are usually not.
- To be precise I wrote 'in books' which record also revenue, not just profits. Increasing cloud revenue is one of the things that drives big corps share price up, the missing bit is that this revenue comes from big corps themself. The growth investors mantra is that as long as revenue is increasing rapidly, they don't care much about today's profits, this is why so many unprofitable companies have crazy high valuation.
- Here is money printing scheme that looks to be at work:
Initial situation:
* Big corp M has X$ in cash where X is huge
Big Corp M invest X$ in AI startup O, with a provision that O needs to use most of the money to buy cloud infrastructure from M to power AI models.
End situation:
* Big corp M has X$ wort of shares in O, the value of which will rapidly grow
* Big corp M cloud division has ~X$ in extra revenue
The deal automatically turns X$ into ~2X$ in books. Rinse and repeat with next round deals and next AI startups. The big corps are reporting increased cloud divisions revenue from AI spent, but it is their own investment money flowing back to cloud divisions.
- Hard to reproduce bugs often depend on an order of events or timing. Different architecture can trigger different order of execution, but this doesn't mean the bug is not in the application.
- Right, there is a reason why print magazines use columns even for long multi-page articles. With long lines, readers tend to get lost when navigating from the end of one line to the start of the next line, and the reading experience suffers. You can help this somehow by increasing spacing between the lines, but the general recommendation is to have 45-75 characters per line.
- You break even, when you break even, the faster it happens the better for your investment. With the current earnings it will take 53 years for investors to break even.