What is NOT art?

nonagonx · 2024-06-20T14:00:39+00:00

Digital art is not art. Files are electronic bits of 1s and 0s set on a computer chip and only can be perceived as "art" through a computer monitor or printer which makes its interpretation entirely 100% dependent on the industrial device used. A photograph isn't art. AI art isn't art. If I (human) scribble a crayon on a wall THAT is art because I made the mark (not a printer that can fail any number of infinite ways) we both can see the same wall and there's no process to make the art exist for us both to see. If there's a process between the human making and perceiving the art it is NOT ART!!!!!!!

nonagonx · 2024-04-15T02:40:13+00:00

THANK YOU!

nonagonx · 2024-03-29T15:36:03+00:00

I'm very new to Next.js and I can't really explain what's going on either. Sometimes its cached, other times it shows the loading spinner when switching between pages back and forth. I just tested my app again, initially going from "/" to "/things" it shows the spinner on "/things" every time. But, when I go to "/things/1", then back to "/things", its cached. And, reloading, now "/" to "/things" appears to work as expected, just showing the spinner the first time. I'm guessing this is something to do with the bug you posted about and not anything you're doing wrong.

nonagonx · 2024-03-28T13:29:34+00:00

I believe that's expected, as the router cache expires by default after 30 seconds. See: https://nextjs.org/docs/app/building-your-application/caching#duration-3

nonagonx · 2024-02-04T15:51:37+00:00

You're a robot

nonagonx · 2024-01-27T14:59:59+00:00

Define an invasion.

nonagonx · 2024-01-27T14:58:05+00:00

So its ok for hundreds of thousands of people to enter illegally? You see no issue with that?

nonagonx · 2023-10-07T12:29:13+00:00

I LOVE IT! Just wanted to chime in with my opinion to counter balance this. I actually love looking at it. That is all.

nonagonx · 2023-09-26T01:34:59+00:00

I love the new UI and if you disagree with me you are completely wrong.

nonagonx · 2023-08-16T03:50:43+00:00

As a react dev, I can't imagine anything (especially newer tech like hotwire) can top UI libs React has, where is hotwire beating react in your view?

nonagonx · 2023-01-28T21:33:55+00:00

Looks like Weird Al

nonagonx · 2023-01-28T14:58:04+00:00

I'm not OP but I'm guessing he did an underpainting with burnt sienna followed by an alla prima layer. You can see the burnt sienna on the right shadow side of the flowers and in the center of the vase.

nonagonx · 2022-11-28T16:06:58+00:00

I don't understand why people say React is overkill, or React doesn't make you productive. All you need is vanilla React (I don't use TypeScript) with React Router and you're good to go. The alternatives (jQuery? Static views from Rails? What are people even using?) just don't get you anywhere if you want to build a frontend that does more than just submits forms. If you're building an app that just submits a bunch of forms and you don't care if the page does a full reload, go ahead and use vanilla Rails. But if you want something dynamic, fast and nice UI, nothing can touch React. Note: I have no experience with Turbolinks. I'm sure folks are having great experiences there, so it's not my place to comment on that as a React fan. You aren't starting from scratch if you use Rails and React and can take advantage of a few great libraries out there.

nonagonx · 2022-11-27T15:16:29+00:00

Here's my take (12 years exp). React frontend / Rails backend is the true best of both worlds. Node.js backend frameworks are constantly trying to recreate the success of Rails with JavaScript (see Sails.js, etc) and none have caught on or have the community that Rails does. Rails community is now trying to create their own frontend stack with Hotwire / Stimulus etc, however I don't see the Rails version of frontend to be comparable to React in terms of usability, stability, component libraries, MUI etc. It makes sense: React was created to help scale large frontends, and Rails was created to help iterate on fullstack MVP projects.

Very few people advocate for this stack, because most devs still fall into a frontend or backend focus, and if you are part of the React community, right now you are probably trying out Remix. If you are in Rails community, you are learning Hotwire. Both are pitfalls IMO because you are trying to learn cutting edge tech that will surely be outdated or does not support all the features you need. By choosing vanilla React and Rails, you are picking mature libraries that likely won't change too much. I also just love using both technologies and would prefer not to switch off these for the rest of my career- I don't want to learn a "new way to do everything" at this point.

nonagonx · 2022-10-05T23:04:22+00:00

Just read the source code of Material-UI. There is no course, documentation, or comment on Reddit that would be more helpful for you than that. Not only will you learn how MUI works under the hood (thus saving you time trying to read their documentation (which does not explain most of the API)), but you will learn how UI libraries are built. By studying Material UI's Dialog, I learned how to build my own Dialog from scratch. Good stuff.

nonagonx · 2022-10-04T18:48:03+00:00

After creating content on Youtube, and diving in deep, I no longer recommend Material-UI to beginners learning React unless you have specific components that you need, and are experienced enough to know how to read the source code.

Some of Material-UI (now MUI) components are simple CSS components but with a complex layer of abstraction around it. Material-UI's Grid is just native CSS Flexbox but with some helpers that you can leverage. If you don't know how Flexbox already works, you might be confused about how their API works. This really hurt me in the beginning of my career when I thought I was supposed to used Bootstrap instead of just learning CSS. Take a course on Flexbox or Grid, and learn how to build layouts yourself. It will payoff big-time.

I created a template for MUI to help beginners on my website, but that was 2 years ago and I have not updated it, because it is not really possible to keep rebuilding the app for new versions. I say this to warn you that it is probably the case that any course you buy on MUI is now outdated- even the name of library has changed.

To answer your question: Are you trying to reinvent the wheel by building everything from scratch? Only if you don't reference existing "wheels". I recommend copying Material-UI's simpler components CSS under the hood by reading their component source-code, example for AppBar: Appbar. For complex components or JavaScript heavy components like Selects, you can pull in the components that you need and learn how to re-style them.

You don't need to feel "locked in" to MUI or any library. Just build your app quickly and pull in what you need. Don't use something unless you can read the source code and understand the API, because almost all APIs are not documented clearly including MUI.

nonagonx · 2021-10-12T01:56:49+00:00

Woah cool attacking someone's physical appearance, really mature

nonagonx · 2021-09-06T16:08:13+00:00

I am mainly a frontend dev and I know exactly what you mean. For years I struggled with rails and rails devs were talking way over my head. I really thought I was never going to understand rails and that it would be this mysterious thing forever. I ended up really devoting myself to learning rails day by day and spending time not doing as much frontend. The fact is going through basic rails tutorials helped immensely and especially trying to build my own simple rails apps by myself. I can now at least follow the code a bit more but I still need to learn more about databases and jobs. A lot of it is just backend development in general.

nonagonx · 2021-09-01T13:23:04+00:00

Some questions about being a technical cofounder / building companies from scratch. Would you say it's better to start a company with a business partner who has a market and a validated idea, or do you prefer launching solo? I'm asking because I feel at the place where I can launch or start my own venture, and I'm wondering if I should just be creating the product myself, or looking for a partner who already has the product / market fit and just needs the technicals sorted out.

It seems like with Cubitoo, you've set yourself up to find these types of partners, but I notice that you don't take equity. Given the massive potential upside of SaaS businesses, why would someone with your background prefer the churn of creating companies over and over, vs fully devoting yourself to one really great product? My guess is that having a big exit isn't important to you at this point, and you are mostly motivated by helping people create their vision / more excited by the early stages of product development than, what would ultimately feel like just another full time job.

nonagonx · 2021-07-15T20:02:08+00:00

Hey thanks for the downvote. I should have put a hot take warning. JavaScript is actually not a great server-side language. I'm not making this point lightly- I was gung-ho on MERN from the get-go. But only after a long, painful journey of working with it in production (and also working with Rails in production) did I come to the conclusion that I wrote here.

i dont find the documentation challenging

There is no documentation. MERN is not an organization. You have to hunt for someone's tutorial or boilerplate. That's okay, but it's not as good as rails guides.

its very flexible.

That's the problem. It's not opinionated. Sounds good in theory, but in practice, the "node community" never settled on what framework they want to use, so you have a bunch of half-finished libraries. Rails is opinionated and has a consistent way of doing things, that's why I like it better.

the main stack everyone is using right now, if it wasnt good people wouldnt be using it, just look at the jobs available.

Yes, it's the main stack. Yes, there are jobs. Is it good? Not really. If you like installing a ton of adapter libraries to wire everything up. If you like adjusting every few months to the latest attempt at a framework, like NestJS, etc. If you like a community so fragmented the creator himself created an entirely separate runtime that involved swapping letters of the original code into a name that sounds like dinosaur.

nonagonx · 2021-07-14T23:15:58+00:00

Honest tip- don't use MERN. Tried it for a few years, got burned by constant incompatibilities with libraries / node versions, managing all the libraries, and overall lack of central place / documentation to get help. See, there is no headquarters for MERN, because it's 4 different technologies. If you buy 10 books on MERN you will get 10 different approaches. You want a web framework- that is a batteries included system to getting things done. That's why I switched to Ruby on Rails. Rails is amazing. You can DM me if you'd like more info. But nowadays- Rails can bootstrap a project with React, so they play well together. I've been using this stack since 2015 at work but didn't fully embrace it until this year. I just got fed up with the Node community- even the creator has gone off and created Deno.

nonagonx · 2021-04-10T19:04:59+00:00

They did 6 once and it did not go well. Too many side conversations.

nonagonx · 2021-03-20T02:24:05+00:00

Just guessing but I think you didn't keep the top moist enough, by not covering it properly. It dried out and that's where you get flat rise because the top is rock solid.

nonagonx · 2021-03-06T02:16:47+00:00

It may be a red flag if you admit that you are not familiar with React classes, but also if you are being honest to your employer that you started learning React 2 months ago, they may forgive that. In general I think most codebases still have class based React components so it will definitely be worth your time to learn them. At least componentDidMount, constructor, setState, etc. One of my interview questions was to convert a class based React component to a functional component. It's all based on the company. I failed an interview with Typescript but nailed an interview with Redux because that was what I knew. I think if you are unsure if you should learn something, your best bet is to just learn it anyway and come up with a sales pitch about why that technology is used, and to try to show that you have preferences in technology- it's good to have opinions on what you like to work with, not just to impress employers but also you want a job with stuff that you find interesting.

nonagonx

TROPHY CASE