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

My wife suffered from PPD after the birth of our first. She also suffered antenatal depression during her second pregnancy.

SSRIs literally saved her life.

The difference to her personality was profound: the woman I knew and loved came back.

Was it a societal structure and support issue? No. She had support from myself, our families, family doctor, her obstetrician and a psychologist. My work provided me with paid time off to manage it. We had no financial concerns; she had 12 months of legally protected maternity leave with the first 6 months fully paid.

She was ill and the medication worked.


I joined a bootstrapped SaaS several years ago in a niche domain. They were making 10x that again in MRR, growing rapidly and still 100%-owned between the 2 founders. VC's knocked on their door every week but they had their own vision for growth.

Don't be afraid to walk your own path.


How were the VCs aware of the MRR of a private company ? I'd assume some external indicator like position in the app store, but outside of that, I'm curious how'd they know ?


It's a B2B product in the FinTech space. UK-registered so their accounts are public.


Manufacturer warranties are in addition to the legal warranty, they can't contract out of it. https://www.accc.gov.au/business/treating-customers-fairly/c...


.net core is cross platform, so this should work on Linux and Mac.


Not only that, .net core is now essentially the only active branch of .net. The windows only .net framework is becoming legacy.


Kind of. .NET Framework will be the XP of .NET until Microsoft provides an actual migration path to many of the APIs and frameworks that haven't made it into .NET Core.

Plus some of those APIs that made the cut into .NET Core, like the UI ones, are Windows only.


There are also some critical tooling gaps that mean .Net Core is still broken for scenarios that worked a decade ago (FSI package management with F#, specifically).


FSI has never had package management. Are you referring to something else?


Sorry for the loose term. Not package management a la NuGet, but how packages and their references are handled (ie managed), so that they're not available and operative in FSI on .Net Core in VS.

Things that work when compiled, worked about a decade ago, but die on FSI preventing multiple data interaction & scripting scenarios. Ref: https://github.com/dotnet/fsharp/issues/3309 , https://github.com/dotnet/fsharp/pull/5850 , https://github.com/fsprojects/IfSharp/issues/206 , etc etc

Specifically, referencing a library that uses an FSharp.Data type provider, and calling that library in FSI in Visual Studio.

Updated to the latest and greatest, 5 y.o. code looks like this when we execute it:

> System.MissingMethodException: Method not found: 'System.String FSharp.Data.Http.RequestString(System.String ....


Basecamp?



It's just become a Stage 0 proposal: https://github.com/tc39/proposal-pattern-matching


Woo hoo, can't wait. Especially with what TypeScript can do with this.


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

Search: