Hacker News new | past | comments | ask | show | jobs | submit | EToS's comments login

Merry Christmas, hands free internet!


Its a great example of how to use design systems


Personally, I'd drop the lifetime access pretty quickly and bank on the fact that customers will renew for a quality product/service.

Last thing you want is an income time bomb in 3 years where your most active and loyal customers no longer need to pay.

Maybe an alternative could be to offer free months subscription and a tshirt for every successful recommendation


I also thought that I would quickly refuse a lifetime deal and already refused. But after 3 weeks I decided to temporarily return them, since there was not a single sale of a subscription, and the extra money will not interfere with me now.


Lifetime annual discount might be more palatable depending on your cost of delivery.

Grandfathering can also be rewarded with a higher referral fee (as long as referrals are active, they can discount permanently).

It takes some planning up front with account, feature and billing management but can be worthwhile in general for flexibility.

While fewer than expected people might activate and use a lifetime deal, the ones that do can be a fun bunch support wise.


I know this sounds shitty but what's to stop you from periodically removing some of the features from the lifetime deal until it's just barebones and no support?


Other than being a decent human being that actually sticks to the agreements they made, nothing. But there is a surprising amount of value in "being a good person" when you're not a mega-corp.


another quick point, if customers are happy paying for the lifetime offer, maybe you can raise prices for the Enterprise offering


Its like paying to be a second class citizen! :)


Every once in a while I think of paying the Workspace ransom, hoping it would keep Google from potentially locking me out of my account for nebulously defined reasons. Then I come across stories like these how Workspace gives you an interior product (and likely no account protection).



VIM = OG

NVIM = A fully compatible re-write with focus on better scripting (lua), performance etc

GUIs = Alternative for using VIM/NVIM inside a terminal, with better optimisation for performance, smooth scrolling, animations etc (e.g MacVim, Neovide etc)


I didn’t know that Neovim was a complete rewrite, thanks for sharing. The fact that I didn’t know while actively using nvim is a testament to the quality of compatibility they deliver.


I don't believe it's a full rewrite. From Neovim's Vision statement:

"Neovim is a refactor, and sometimes redactor, in the tradition of Vim (which itself derives from Stevie). It is not a rewrite but a continuation and extension of Vim."

https://neovim.io/charter/


apologies, yes i believe its a fork


ahem, full history:

ED = OG

EM = Modified ED

EX = Extended EM

VI = Extended EX

VIM = Imitation of VI

NEOVIM = Vim fork


Vi is short for "visual."


> A fully compatible re-write

I don't think this is entirely accurate. The projects have diverged somewhat, so I'd call Neovim a "mostly compatible fork".


The Neovim hard fork is not fully compatible, nor is it always better performing. I also do not find that Lua is better for scripting overall, because there is an impedance mismatch when you need to interact with the editor model. (If you’re doing just programming then, yes, it’s better. But it’s the interface layer which is difficult, and which I find worse than Vimscript or Vimscript9.)

MacVim is a macOS packaged version of Vim with (fairly) light customizations of gvim which is part of the vim source bundle. All neovim GUIs are from-scratch constructions because the neovim developers decided that they did not want to support GUIs directly. IMO, this was a mistake, because none of the neovim GUIs that exist work as well or are as well OS integrated as gvim or make for as "easy" packaging as MacVim has.


Neovim also has some surprising feature regressions compared to Vim. I tried switching to neovim for a while until I realized it was silently removing all ACLs on edited files and breaking services for me. Looking into it, I found that, for no clear reason, ACL handling was removed early on in neovim, and a bug had been open about it, with multiple pull requests that were never merged, since 2014 (https://github.com/neovim/neovim/issues/1200). Vim has never had a problem with this, as far as I know.


My favourite is "it's not a bug, it's a feature" under issue reporting broken bang commands (https://github.com/neovim/neovim/issues/1496)


Wow, its in 2 hours.. that's Blazingly fast


That's what happens when you use coconut oil


I see you've been around the block a few times


The name...


Could be an interesting marketing approach for a Security/Pen Test SaaS.. Heres a vulnerability, pay for our service and we'll provide a full report.


I get spam for that all the time - both for "pen test" and for "seo test".

Basically someone fires up a tool that checks a few things mentioned in a best practices document somewhere, scans as much domains as possible, and then sends out emails with the (subset of) the results.

Invariably, the results are false positives but hey, if you don't know that, they might get a new client. They'll file the (automatically generated) report and presto, easy money and a chance to upsell a retainer.


its a shame they didn't move to having a CC linked to the account, and keeping the free dyno tier


At a guess, there are a few things which "could" be working against you:

- Leadership at certain companies can include a lot of people management, and so being in a team of one possibly does make the case for progression in the eyes of HR.

- The company isn't big enough to facilitate career progression for everyone.

- The project may be seen as innovative, but possibly something that will be absorbed into the best practices of all teams over the coming years, and so there may be less of a case to promote anyone in the team because of this. (this is where you need to read between the lines a little, as PO's will omit plans like this for obvious reasons)

- Unknowns.. the people who briefly worked on the team may have raised concerns during 1-1's / exit interviews that you're unaware of.

The best advice i could give is to leave any frustration at the door during the next few months, and keep an eye open for you're dream role at another company.


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

Search: