1,972 karma · joined May 25, 2015
> Most of the time, you can tell easily if a website is running with Bootstrap or not, even if you’re not a seasoned developer. From my perspective, it doesn’t always sound like good news! Because when using it, websites tend to look the same.
Which is often fine for internal or B2B. For B2C, a unique look may be more important. Many apps are LOB, internal dashboards, B2B SaaS. Often customizing the brand colors is enough.
> With Tailwind, however, you can add your custom styles to almost anything. Why is that so important, you ask? First, because it allows you to design the website how you want it, this is great, especially for designers!
I'd say it's mainly great for designers, although there'll be overlap with developers for certain use cases. With the kinds of projects I work on, I don't generally find myself needing that. When I do, editing the CSS is easier than bringing in Tailwind.
> Look at easy it is! I don’t need to write custom CSS or Sass code. I just need to call the right classes to be able to use it. It’s really, really simple and yet powerful!
This is a bit handwavy. It isn't easier to use Tailwind vs. custom CSS per se. Do away with custom CSS and you're now just writing custom Tailwind. That could be good or bad depending on your team and tooling.
The more low-code/no-code SaaS products I've tried, the more I value it. LC/NC SaaS generally is expensive and inflexible. Everybody knows Excel, it's dirt cheap, and it just works. It's part of a certain IT subculture to bash it, but I stopped laughing along.
Excel is great at what it does. Love seeing clean solutions like this that give it even more muscle.
> In academia there are definitely people who are heads and shoulders above others, for example [my emphasis].
GP was providing support for their claim that 10xs exist in most fields. Academia was just one example of a field (or "field of fields"). The same could be said of farming and plumbing.
"These people" don't deserve punishment any more than a developer who had to make a tough decision does. It's the same situation at a different level with more visibility. Management has its own set of challenges.
> that's "only" 6 billion dollars to keep those "great" people that they "love" working
It wouldn't be fair to them to keep them employed if doing so meant weighing down the company, which could eventually cost everyone else their job. Better to have strong companies that continue to adjust to fit people's needs and let workers move among them.
> these antics require revolution
Revolution to what economic system, exactly? I don't want to live in a world where companies are forced to keep workers in unproductive jobs out of a misplaced sense of goodwill. That sinks the ship for everybody.
There are differences, but the similarities are more than superficial. Some of my first apps were in 6, and then I transitioned to VB.NET in the early 2000s. At the very least, it pretty familiar and intuitive.
Even VBA is pretty similar to the VB.NET apps I developed in terms of OOP, syntax, autocompletion in the editor, event handlers, and so on.
Again, there are definitely differences, but there was no "[relearning] software development and getting intern like opportunities" like the comment I was replying to said, and my knowledge and experience was definitely not "worth exactly zero." It was just an evolution.
Except that didn't happen at all. Visual Basic still exists.
From Microsoft (2020):
> One of the major benefits of using Visual Basic is that the language has been stable for a very long time.
(Source: Microsoft, on Visual Basic support in .NET 5: https://devblogs.microsoft.com/vbteam/visual-basic-support-p...)
As of January 2023, the latest version of Visual Studio (2022) still offers to scaffold me a new Visual Basic project!
And VB exists in other forms, too. The other day, I was coding VBA macros for an Excel spreadsheet for my business. Worked great and saved me a bunch of time.
Laravel Livewire is pretty nice for basic interactivity, which is all many sites need, but React becomes useful as soon as you start needing app-like features. At that point, using Next, which is already plugged in to that ecosystem, is a very nice experience.
Next is great for static sites, too, so nowadays I prefer putting my time into that vs. fragmenting between a more purely server-side framework like Laravel.
Facets of agreeableness include altruism and compliance, which are two very different things. Someone may be altruistic while also breaking the rules. Someone else may be compliant but stingy. But both could score high in agreeableness.
Agreeableness in the five-factor model (Big Five) doesn't necessarily mean being overly compliant; it can also mean being trustful or altruistic (trust and altruism being two facets of agreeableness).
The study uses five-factor terminology with participants completing the Big Five Inventory (BFI) and some also completing the NEO-PI-R, so those are the definitions to keep in mind here.
Maybe it is, but now my head's going to insist on "Danjee," rhymes with Angie.
Hacker News, a.k.a. DanG's List. ;)
Sincerely, thanks, Dan, for all you do here. HN has some of the most polite and thought-provoking online discussions I know of thanks in no small part to your work, and I come back year after year for it. You've helped make this place a hugely valuable resource and just a genuinely nice hangout spot. Thanks again and Happy Holidays to you and yours.
On 1, human artists are copying copyrighted pixel data into their system for training. That system is the brain. It's organic RAM.
On 2, money shouldn't make a difference. Jim Carrey should still be allowed to paint even though he's rich.
If Jim uses Photoshop instead of brushes, he can spit out the style ideas he's copied and transformed in his brain more rapidly - but he should still be allowed to do it.
Next isn't really like Angular in that you don't need an API layer (though you can have one if needed). It's more like ASP.NET Core MVC.
The difference is the frontend code is truly integrated with the backend. It all lives in the same project. It's just React components. You can render them statically on the server at build time, per request at runtime, or on the client. And you can mix and match. Next only ships the client the JavaScript it needs.
You don't need an API unless you want SPA parts of the app. Where you do want that, it's simple to implement, because you're already in JavaScript and all your other code plays nicely with it. It's a really nice way to organize and consolidate the different pieces of web dev IMO.
That just sounds like mandatory busywork that may or may not prevent poor programming practices. I'd rather pick a framework for productivity.
> 2. Mapping requirements of this type are much too trivial to base a tech stack choice on.
Trivial for large corporations with money to burn, maybe. A huge time-waster for my startup.
> 3. If this model syncing was really an issue (it usually isn't) you could try Blazor.
Blazor is cool, but the bundle sizes are still too large right now, and it doesn't have the ecosystem of web components that JavaScript does. Sure, you can integrate, but you're just making life more complicated for yourself. It feels like too little, too late.
The grass isn't greener. I've built in both - I have a .NET Core/Angular SaaS app that I created and sell, and I've been building greenfield in Next. I much prefer Next.
The duplication in .NET/Angular has never been worth it...not once. And having network calls for everything is unnecessarily painful.
I started the app in 2019, when RESTful SPAs were all the rage. I bought into the hype that you should have API endpoints for everything no matter what, because you'd soon have a mobile app and daemons and this and that.
Turns out, YAGNI. It would've been better to server-side render and only create API endpoints when necessary.
That's what I like about Next: Static generate where you can, server-side render per request where you can't, SPA where necessary - and the layers are as flat as can be. It's the best of all worlds.
That being said, I've worked in .NET for ~16 years now, and I like it more than JavaScript/TypeScript. But I'd still rather develop a web app in Next and put any background services elsewhere in .NET if needed.
With ASP.NET, a React/Angular project is separate, there's a separate model layer, and you have to keep that in sync with the .NET models.
With Next, there's true code reuse between client and server. Next is smart about shipping your code where it needs to run, server, client, both. You can even mix and match from page to page: Server-side render one page per request; statically generate another at build time.
As much as I like ASP.NET, Next has leapfrogged it for web apps.
What I like about Node, though, is frameworks like Next.js that are the best of both worlds. You can do traditional server-side rendering using React components, so you can easily add as much/as little client-side JS as you need.
With Next you use the same package manager for the front end and back end. And you get code sharing and access to that huge ecosystem of libraries.
But needs and skillsets change the equation, definitely.
That said, I don't think it's as bad as this article makes it out to be. There's this kind of maintenance in a traditional server-rendered Django/Rails app, too, on both ends. You can self-host your JS scripts or fetch them from a CDN instead of using Node, but they're still deps. You still have to worry about upgrading and vulnerability scanning. It's just invisible now. The onus is on you.
> How is Wasp different from Next.js / Nuxt.js / Gatsby?
> TL;DR - These are frontend-first frameworks, with some limited backend capabilities.
> [...]
> Although some of them now offer an option to use serverless functions, you still have to bring your own database and you'll also need some kind of a server/backend if you'll need to run more complex operations.
That's a big understatement; Next is fully full stack. You get API endpoints and server-side rendering out of the box.
You can deploy the backend as serverless functions, yes, but you can also deploy it as a plain old Node app.
Does Wasp offer something on the backend that Next doesn't?
> you still have to bring your own database
Confused on this one - does Wasp abstract away the database? The docs show a database connection config and mention using Prisma as the ORM. It looks similar to what I'd do in Next.
> If I need assistance, I will most likely do one of the following:
>
> Find a support e-mail.
> Go to a physical store.
> Ask a friend.
> See if I find an unintrusive live chat that I chose to enable.
This is a developer mindset: take the time to solve the puzzle. I get it, but the majority of people don't think that way.
Most people don't want to solve the puzzle. They want to buy the product and get on with their day. Live chat lets them do that, and by the numbers, it works.
OP's startup idea is in a well-understood domain. There are lots of existing competitors offering basically that exact service. There are clear, obvious paths to building it. GPT can draw from blog posts and tutorials.
On the other hand, it does poorly with significantly novel ideas. I tried it with one I've been working on that combines 3D printing and crafting in new ways. Its answers just regurgitated blog posts about existing combinations. It even ignored the grammar of my questions, which switched the usual direct object with the object of the preposition. Which makes sense, because it isn't doing critical thinking - it's pattern matching.
Either way, soy vs. meat is not the dichotomy it's sometimes presented as in political narratives. You can eliminate both and still have a huge number of healthy world foods to choose from. The Mediterranean I had recently was delicious and soy and meat free.
[0]: https://www.jwatch.org/jw200808070000002/2008/08/07/do-soy-f...
His experience in tech doesn't sound so charmed to me. He was obsessed with climbing the corporate ladder. He slept in the office and woke up early every morning to start grinding again. He worked so much he didn't even have time to play a game with his son.
He tried another kind of work to see how it compared, and he learned stuff. There's nothing patronizing about that.
While that's certainly possible, it depends on humans choosing to put AI in charge of that important function and the function being important enough to eliminate humanity before the AI can be shut down. In other words, don't build Harlan Ellison's AM and "I Have No Mouth and I Must Scream" won't happen.
Inaccurate science communication like this is a big problem - laypeople read the headline and start to irrationally fear and oppose AI in general, when the prediction is only about a highly specific, ill-advised use case.
Does a consumer have any insight into what the model does/doesn't like about an IP, or is it a black box?
I'm wondering how they could contextualize a score for their use case, or how I as the IP owner know what to fix to raise the score.
Threats: 0
Trust score: 0 - High risk
I'm confused why it's considered high risk if no threats were detected. Maybe unknown IPs are considered high risk until proven otherwise?Fot me, the spam that makes it through all comes from Gmail addresses. Maybe the filter is more lenient with Gmail accounts.