Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A new blog for 2024

chrisnicholas.dev

Post reply on HN
Print view View original

71–80 of 114 posts

Re: A new blog for 2024

#71

Post by joshmanders »

brigadier132 wrote: post #68
joshmanders wrote: post #58

Earlier quoted context omitted.

> Wordpress and php are negative value skills, you do not want to advertise that you know those things as a developer because someone might try to hire you for them. This was unnecessary.

It's the truth, the jobs that use php are not the ones I want to work in. People are saying php is actually good nowadays but I have no reason or desire to learn it. I don't want to learn or work with wordpress, I already know as many scripting languages as I need to know, and there are no companies I want to work for that use php. I'm already in the part of my career where learning another programming language is no…

Your personal view is not widespread though, your original message would have been better left off with out bashing PHP because YOU don't find a use for it.

There's billions of dollars in revenue generated yearly from PHP sites. And not just "legacy" either, I'm talking evergreen PHP apps being built and generating revenue.

It's just as alive and well if not even more alive than some other languages people prefer over it.

Re: A new blog for 2024

#72

Post by xmprt »

joshmanders wrote: post #60
dmje wrote: post #48

Earlier quoted context omitted.

Again, pretty hilarious given how full featured and fast PHP is nowadays, but ok... I'm also gonna make a little private bet that PHP will outlast a fair amount of the currently trendy tooling...

I'm with you on the anti-PHP hate, but FWIW PHP and JavaScript came out exactly 6 months apart from each other, and one is the only way to code in the browser, so I'd say both are pretty likely to last a long time.

I don't know much about the PHP landscape but at least with Javascript it seems like trendy frameworks change every 5 years. JS -> JQuery -> AngularJS -> React -> Angular 2 -> React Hooks -> Next -> ... Feels like the "right" way to do things keeps changing.

Re: A new blog for 2024

#73

Post by pvg »

FalconSensei wrote: post #70
pvg wrote: post #35

Earlier quoted context omitted.

Please don't post shallow dismissals, especially of other people's work. https://news.ycombinator.com/newsguidelines.html

Author mentioned that the reason for the new blog is to be easier to create posts. But doesn't mention much of what changed in the workflow. Seems he's using md files. But then what was he using before? If MD->MD, then what changed? Using Obsidian to be easier to edit and sync between devices?

The author is in the thread so if these are your specific questions or critiques, you should direct them there. 'It's hilarious to me they don't use Wordpress' is not a specific question or critique, it's a generic sneery putdown.

Re: A new blog for 2024

#74

Post by joshmanders »

xmprt wrote: post #72
joshmanders wrote: post #60

Earlier quoted context omitted.

I'm with you on the anti-PHP hate, but FWIW PHP and JavaScript came out exactly 6 months apart from each other, and one is the only way to code in the browser, so I'd say both are pretty likely to last a long time.

I don't know much about the PHP landscape but at least with Javascript it seems like trendy frameworks change every 5 years. JS -> JQuery -> AngularJS -> React -> Angular 2 -> React Hooks -> Next -> ... Feels like the "right" way to do things keeps changing.

The "right way" is subjective and the first mistake many people make IMO. What I think is the right way isn't always the right way for other people.

Tooling changing in JavaScript is unique to JavaScript only because of the language constraints. PHP, Ruby, etc are all controlled by the developer, whereas JavaScript is controlled by the browser vendors and end users of those browsers. You have more things to work around, inconsistencies to smooth over, and more importantly larger ambition on the frontend than most things can currently support, so new paradigms and frameworks come out to tackle that.

Also 5 years in internet time is a long time. So I'd probably not say it "changes so fast"

Re: A new blog for 2024

#75

Post by FalconSensei »

slothtrop wrote: post #27
skydhash wrote: post #25

Earlier quoted context omitted.

Not really, wordpress is a bit of nightmare to code upon and buying plugins and themes can result in incompatibility issues and vulnerabilities. I think Medium is easier, but it’s a walled platform.

Substack seems increasingly popular, though not among devs for some reason.

Keep in mind that recently Substack said that they allow Nazis and wouldn't remove them

Re: A new blog for 2024

#76

Post by paczki »

Love this! Love the design and font are fantastic choices as well. I actually just started last week building film grain into my current WIP and it really feels like it catches the eye so much more. Largely inspired by trying to make super high quality photos feel vintage by blurring + adding noise.

Exciting to see what more comes whenever you post. Digging this cursor blog as well.

Re: A new blog for 2024

#77

Post by wiseowise »

> I’m applying a tiny amount of film grain to the body. To me, this makes the page feel like one consistent piece; as you scroll down, the noise sticks to the content, somewhat similar to seeing texture on paper.

That’s a really nice touch. It does help me with reading, kudos.

Re: A new blog for 2024

#78

Post by rambambram »

fouronnes3 wrote: post #65
rambambram wrote: post #45

Earlier quoted context omitted.

What about a background (pattern) that has the noise already in it? I use https://bg.siteorigin.com/ often to create subtle backgrounds like the one on https://www.winkeljustitia.nl/

I was thinking maybe there's a pure CSS way to do it? That seems to be inline with the style of the author's blog.

Pure CSS would be nice indeed.

Re: A new blog for 2024

#79

Post by p4bl0 »

wiseowise wrote: post #77

> I’m applying a tiny amount of film grain to the body. To me, this makes the page feel like one consistent piece; as you scroll down, the noise sticks to the content, somewhat similar to seeing texture on paper. That’s a really nice touch. It does help me with reading, kudos.

I did the same thing a few months ago on my web page https://pablo.rauzy.name/ (well, not on the home page but on all other pages), for the same reason :). The texture is not noised because it is just a CSS trick with background properties so it is quite regular, but I feel like it does the job.
Post reply on HN