Hacker Newsnew | past | comments | ask | show | jobs | submit | ekinertac's commentslogin

I have used a couple of laptops with touchscreens, and the experience was awful, even with the latest technology. If Apple gave us an iPhone or iPad-quality touchscreen on MacBooks, I am 100% sure the experience would be perfect.

I have a laptop with a touchscreen that I regularly forget is a touchscreen until I accidentally touch it.

Same. My work laptop has a touch screen and every now and then, when I remember that fact, I’ll use it to scroll through a few pages of a PDF. It gives me a chuckle because it’s so inefficient and inaccurate… then I immediately revert to my click-wheel mouse.

there are hardcoded elements in the repo like:

/Users/dvirdaniel/Desktop/zuckerman/.cursor/debug.log


thanks


the real question isn't "should AI write readable code" but "where in the stack does human comprehension become necessary?" we already have layers where machine-optimized formats dominate (bytecode, machine code, optimized IR). the source layer stays readable because it's the interface where human judgment enters.

maybe AI should write better readable code than humans. more consistent naming, clearer structure, better comments. precisely because humans only "skim". optimize for skimmability and debuggability, not keystroke efficiency.


i had to ask, do you have any paying customers?


encountered this post in reddit maybe an hour ago. the comment sections are very different. i'm gonna stick with HN for sure.

good project though. using copier instead of cookiecutter is a good choice.


It was all great on Reddit, though until some folks decided to downvote for no apparent reason and then deleted their accounts.

I've chosen copier because of all the pain I've gone through for years just to keep my template and projects running in parallel updated.


one small note, you should move quick start section in README to be seen earlier


Thank you for your suggestion. I'll update the README so that people can hit the ground running faster!


20 years is an eternity in web development, and Django's longevity is a testament to its brilliant design philosophy. Happy birthday to the framework that gets things done.

Django is pragmatic, secure, and unbelievably stable. It's the framework you choose when you want to build a real business, not just chase the latest trend. It has powered some of the biggest sites on the web, and it's still the best choice for a huge number of projects.

Here's to 20 more years.


Wasn't Django inspired from Rails


Not exactly. Development on what become Django began sometime in 2003, before Rails was released.

Certainly the release of Rails — and, more importantly, the questions in the Python community about what _our_ web dev story would be — inspired us to extract the framework from the rest of our code and release it. And over the years we’ve taken some inspiration from Rails (as well as anywhere else we see good ideas). The biggest one probably being the basic ethos that web development should be easy — the focus on what we now call “Developer Experience” is the best thing Rails gave the world, I think.


Not really, it was a strong inter-connection between the two at the beginning, going both ways, but I'd say that Django's design philosophy was its own thing. Granted, as time goes on things have started to become fuzzier and fuzzier in my head, and not only when it comes to programming languages/web frameworks and the like.

Source: me, I was programming in Zope 20 years ago (mostly hated it, although there were lots of interesting things in at a conceptual level), switched jobs at the beginning of 2006 and thanks to the new boss I got to use Django since February of 2006 (I think I still have a 0.96 version installed somewhere on an old instance, still does its thing).


Zope, shudder. It had some amazing ideas and I built a reasonably large app on it, but I’d rather swallow my own tongue than work inside an application server again.

Django and its contemporaries, like TurboGears and Pylons, were a breath of fresh air.


I liked Turbogears, but their approach of using "best in breed" libraries kinda burnt them as what that meant kept changing and leaving them behind.


It did. I think it was a great idea but other things skipped past it. I used Pyramid for a while and still appreciate it, but I can't imagine using it for my own new projects in a world where Flask and FastAPI and others exist.


Logitech MX Keys S and MX Master 3S all the way. the only problem i have the rubber on the MX Master 3S. if they make a hard surface one. i'll ditch mine in seconds.


that is just amazing (;_;)


thank you so much!


alias bat=cat alias frep=grep

and i'm good to gp


what a briliant idea, most of my meeting i had to share my 4K screen with laptop pals and most of the time i had to zoom so they can see. now it's solved.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: