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

I tried Vivaldi a couple of years ago and it was slow as fuck

The UI was written in Javascript I believe. At least a few years ago when I tried it. I was pretty happy with it except for the lag which made it unusable on my hardware.

It is very much in the spirit of the old Opera browser. I miss the days when software was trying to be as cool as possible instead of trying to be as lame as possible. (God what a concept!)

It's good to see someone still trying.


Python is faster to write so obviously you'll see things built in Python first more often than the reverse. What's that quote -- "Better to remain silent and be thought a fool..."


Indeed. Python is faster to write and harder to maintain over the long run.

The "faster to write" advantage becomes less relevant if most code is going to be auto-generated.

The "harder to maintain" might still remain more relevant.


>harder to maintain over the long run.

First off, this is begging the question. Second, if you never get to a point where you need to maintain something, who won?


No


Guess what, human couriers use the sidewalk


A vending machine is not a human tho.


Human couriers also walk on the sidewalk.


Paywall


My god this title cliche is annoying


"Python doesn't have inbuilt types"

False.


If the maintainer merely doesn't fix the bug, then yes. If they close the bug report so it gets lost and other contributors are discouraged from working on it, then no.


Closed reports are not lost, they are still searchable/linkable, they are just not in the list of work to do.

This is entirely up to the maintainer, who puts in the work and gives up their time/money to do so. If you want to be in charge on a given repo, put in the work and become a real contributor, if not accept the rules the maintainers choose.


You know what I mean. If the issue is closed, it looks like it's been solved. A new issue may be created that duplicates it, etc.

Obviously it's up to the maintainer. I'm saying what the maintainer should do, not what they can do.


Dupe reports are a signal all by themselves, that's really not harmful, nor does something being closed implied solved.

You shouldn't presume to know what is best for an open source maintainer of any given project - projects vary, reports vary in quality, and the job of maintenance is not an easy one.


For feature requests, sure, but not for bug reports


Who are they?


As far as I can tell, the following names all refer to the same person:

- lovelydinosaur,

- Mia Kimberly Christie

- Kim (Christie)

- Tom Christie


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

Search: