1,789 karma · joined July 17, 2008
Maybe that would be a fun concept. A game where the players would start with 1 year on the clock?
A lot of GUI based programs should think of implementing parts of it as a library others can use. I remember early Git implementations in IDEs where they just ran git commands in the background and parsed the command line output. Imagine if the same had been done with SQLite, would it still be as popular today?
I don't have much experience with creating desktop software, but it seems to me that separating the GUI from the "engine" would bring other benefits too.
I have often looked at OSS and wanted to use parts of it myself. An email client might have a really good mail parser that handles encoding, attachments etc. But decoupling it from the rest of the program would take too much time.
The "correct" modern way is the same as in English.
It was more popular in the past, but is still used in many dialects.
It's similar to the "count to ten" principle, before yelling at someone.
If they breach the walls and actually enter the interior of the castle, they have already lost and no staircase design can save them.
It's more complex than Caffeine, but it has a lot of options.
It can also run as a proxy and generate the mocks from actual http requests passing through the proxy
Perhaps this could be a simple button that the users can choose to click instead of a configuration?
Another suggestion: It can be a bit hard to see the shape of pieces with a dark colour, on a black background. Perhaps you could add an outline when you click on the piece to make it clearer? I know we can switch between light and dark background, but the white background on a large screen can be a bit too much
Norway and other countries have a deposit system where you pay extra per bottle, and then get the money back when you return them. Places that sell these products are required to accept any bottle that their customers bring them, so most of them want to use these automatic machines to avoid hiring extra staff.
https://www.youtube.com/watch?v=ZI7OldXuq7c
These machines have existed since the 70s, but the modern machines are of course much more intelligent than the early models. They used to accept glass bottles too, but they are not part of this system anymore. (glass is recycled separately)
Tomra is one of the larger manufacturers:
All trends show that the countries with low levels of poverty, high levels of education and women equality results in fewer births.
Women are able to have careers and want to finish their education and get work experience before they think of children. In countries like Scandinavia, the average age of first time mothers are increasing year by year. We also see that cities within the country with a lot of highly educated jobs have a higher age than others
var list = List.of("carrot", "fox", "explorer")
You are right about the builder, but most projects I have worked with use Lombok and the @Builder annotation to generate the builder automatically. I agree that a native syntax for this would be better.Unless you build a side project to learn a new technology, you should use something "boring" that you know well.
Here's my personal choices in preferred order:
1. Static web sites - Just upload to S3 behind a CDN and forget about it
2. Server rendered website - PHP. It may not be something you brag about, but in my experience it just "works" and has excellent uptime.
Note: If I had to recommend something to a larger organization, I would probably suggest Next.js to attract developers. PHP is often associated with "old school" tech
3. REST service - Spring Boot. I have so much experience with it and there are so many Spring projects that supports a huge range of technologies from monitoring to data
4. Scripts - Python
----------
Static website:
1. Setup NginX using a symlink to the current version
2. Copy the new files to a separate folder
3. Change the symlink to point to the new version
----------
REST service (behind NgninX reverse proxy):
1. Current version runs on port X.
2. Deploy new version and run it on port Y.
3. Update NginX config to use port Y and reload
4. If you need rollback, just reverse step 3.
This can be done using scripts or Ansible too if necessary.
The buildings had already existed for a long time when the Vikings visited. It is unlikely that they would have seen them in person, but stories could have travelled for generations over long distances.
The first pyramids in America were built 1500-2000 years before the Vikings. We are closer to the Viking age, than they were to the first stone buildings at the time. I don't think we should underestimate how far stories can travel given enough time.
I believe many React Native, Electron and other hybrid solutions are made by people like me, who don't want to spend huge amounts of money to test an unknown piece of tech. These people also make recommendations to the companies they work for, which would actually afford to buy these licenses.
Why not think of a "discount" as part of the marketing budget? How much money do they spend on marketing and sales to get new customers? They will get new developers who will improve the branding and gain new "leads" organically.
A viable alternative would need to be just as simple, and currently that implies it should probably be implemented in PHP, which will exclude developers who want experience with "blog-friendly" languages.
One example is the pause screens in Netflix and other streaming services. I sometimes want to pause the screen to read a letter or examine easter eggs left by the movie producers. I can't do that, as Netflix has a semi-transparent overlay with lots of unnecessary graphics and voting buttons.
Half the screen is also covered with the logo and/or poster from the movie I'm currently watching... as if I need to know?
They could at least provide an option to remove the graphic if you actually want to look at the paused movie.
Quote from 10 years ago:
> The system [LMAX] is built on the JVM platform and centers on a Business Logic Processor that can handle 6 million orders per second on a single thread. The Business Logic Processor runs entirely in-memory using event sourcing.