Not sponsored or anything, just a happy customer.
553 karma · joined March 9, 2016
Not sponsored or anything, just a happy customer.
EDIT: Ah, it's not sold for the US market, so that's how.
I actually think this is pretty useful information. It helps you evaluate whether an MCP server is worth the context cost. Similar for getting a feel for how much context certain tool uses use up. I feel like there's a way you can change the system prompt, and so that helps you evaluate if what you've got there is worth it also.
A big realization I had was that doctors don't necessarily start by prescribing the medication that's most likely to help, they prescribe the one that's got the highest expected benefit to negative side effect ratio.
I imagine someone out there does a cost-benefit analysis to compare this system to just fully treating and reusing the wastewater and thus needing to desalinate less saltwater.
Anyways, excellent work!
I've often found myself wanting to edit SVG code directly while viewing the result. This maybe not the most common approach, but sometimes you want to be be dealing with specifics that relate to the fact that you're working with an actual SVG file, and not just a vector image.
So at least back when I went there, basically any CS student could have told you that this website was a horrible idea that is sure to get you in trouble.
I think the confusion might come from the Calorie/calorie difference, i.e. 1 Calorie = 1000 calories = 1 kcal.
That said, I have liked my experience with bidets.
At least that's how I remember writing php in high school.
On the other hand, if you have nothing, I don't think that the fastest/easiest way to a mildly dynamic website is to use PHP.
I got curious about the most minimalist setup I could get for running a static site that would also easily transition to becoming dynamic piece-by-piece. Here's what I came up with using NextJS:
1. Create a `package.json` containing:
{
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start"
},
"dependencies": {
"react": "^18",
"react-dom": "^18",
"next": "14.2.4"
}
}
2. Create `app/layout.js` containing export default ({ children }) => children;
3. Create your home page at `app/page.js`. This is pretty much just what your index.html would have been before except it's wrapped with `export default () => (/.../)`: export default () => (
<html>
<head>
<title>Home</title>
</head>
<body>
<h1>Home</h1>
<p>Welcome to our website!</p>
</body>
</html>
);
4. Put the rest of your static files in `/public`Now, when you want to make one of your html files dynamic:
1. Move it from `public/your-page.html` to `app/your-page/page.js`
2. Wrap it with `export default () => (/.../)`
And there you go, you can start using JavaScript and JSX in your page.
Here's a summary of the differences between this approach and creating a PHP-based site:
1. You have to create 2 more files containing 13 more lines of code than you would with PHP
2. You need to find a NextJS web host rather than a PHP web host
3. Your dynamic pages are html-inside-javascript rather than php-inside-html. You are also technically writing JSX and not HTML, which has slightly different syntax.
4. You have a much easier to set up local dev server (Install `node`, then `npm install` and `npm dev`)
5. This framework can scale pretty seamlessly to "highly dynamic", whereas with PHP you'd probably need to introduce a frontend framework if you wanted to create something actually "highly dynamic".
6. You only need to learn one programming language (JavaScript) instead of two (JavaScript and PHP).
Just felt like doing the math on that one.