TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The Untouched Goldmine of F#

38 点作者 rmanolis4 个月前

13 条评论

jamalaramala4 个月前
&gt; The question is: Why companies moved from monolithic to microservices? What do they try to avoid?<p>One of the main reasons why companies move from monoliths to microservices is to promote ownership and accountability in large codebases.<p>In a monolith where everyone owns the code, developers can break each other&#x27;s code.<p>With microservices, each team becomes responsible for one part, and (as long as they keep their SLAs) they can&#x27;t break each other&#x27;s code.<p>When something fails it&#x27;s easier to identify who needs to fix what.<p>Microservices don&#x27;t make much sense for small teams if they don&#x27;t need or don&#x27;t have the headcount to split responsibilities.
评论 #42725936 未加载
评论 #42726166 未加载
评论 #42726961 未加载
评论 #42725714 未加载
评论 #42726126 未加载
评论 #42726234 未加载
评论 #42726414 未加载
boxed4 个月前
&gt; It may not have the information on the filename or the line of code like the ordinary stack traces, but these are useless information anyway.<p>That is the weirdest and most crazy thing I&#x27;ve read in years.
评论 #42725517 未加载
评论 #42725308 未加载
评论 #42726297 未加载
评论 #42725272 未加载
jitl4 个月前
So… if I ever decide I want to change the call stack of a lower level function… I’m going to break types that all my callers and callers’ callers and callers’ callers’ callers’ are depending on? Like, my call stack is enshrined in a type so that to change it means a refactor all the way up to main()?
评论 #42729837 未加载
agentultra4 个月前
Is TST essentially the validation monad[0]?<p>Glad to see more folks finding and appreciating FP languages like F#. It&#x27;s good stuff. Scott Wlachin has a great site to discover more F# goodness[1].<p>[0]: <a href="https:&#x2F;&#x2F;hackage.haskell.org&#x2F;package&#x2F;monad-validate-1.3.0.0&#x2F;docs&#x2F;Control-Monad-Validate.html" rel="nofollow">https:&#x2F;&#x2F;hackage.haskell.org&#x2F;package&#x2F;monad-validate-1.3.0.0&#x2F;d...</a><p>[1]: <a href="https:&#x2F;&#x2F;fsharpforfunandprofit.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fsharpforfunandprofit.com&#x2F;</a>
评论 #42727395 未加载
cies4 个月前
&gt; only Odin, F#, OCaml and Zig have [Tagged Unions or Discriminated Unions]<p>The good old missing sum type story.<p>Don&#x27;t Rust, Haskell, Elm, Kotlin (with sealed classes), etc also have them?
评论 #42725363 未加载
评论 #42725947 未加载
talles4 个月前
&gt; It may not have the information on the filename or the line of code like the ordinary stack traces, but these are useless information anyway.<p>These are useless information?
seamossfet4 个月前
God I remember having to deal with F# when I was an intern, what a nightmare. It&#x27;s like the worst parts of Java and C# smashed into one esoteric language.
kkukshtel4 个月前
C# has a much awaited and active proposal to add DUs to C# so I suspect C# will also support this once live (and continue its legacy of plucking great features from F#).<p><a href="https:&#x2F;&#x2F;github.com&#x2F;dotnet&#x2F;csharplang&#x2F;blob&#x2F;main&#x2F;proposals&#x2F;TypeUnions.md">https:&#x2F;&#x2F;github.com&#x2F;dotnet&#x2F;csharplang&#x2F;blob&#x2F;main&#x2F;proposals&#x2F;Typ...</a>
garganzol4 个月前
Another reason why companies moved to microservices is because it is easier to manage smaller projects. Services have stronger boundaries, they can be swapped with newer and alternative implementations, it is possible to combine the power of different technologies.<p>I came from the other side: I own a huge monolithic web behemoth which is almost unbearable to maintain now. It was built using a now outdated technology, but: it serves customers, it runs the business, it brings profits. Nevertheless, it is a huge pain to even try to change something in it. The project is at its dead end now, it is a one-trick pony who has become too old.<p>Nowadays I build newer parts using separate well-defined services. It is not textbook microservices, I would call it just services. Imagine building a mini-product that is not publicly available and only used internally. This kind of productized services work well enough to never look back at the fragile monolithic approach.
Nelkins4 个月前
I upvoted this because I love F#, but I can&#x27;t say I agree with the conclusions of the author.
troelsSteegin4 个月前
This is really about making stack traces easier to understand.
评论 #42725243 未加载
jcmontx4 个月前
I really like F#, but I really miss having a full fledged f#-native ORM
评论 #42725198 未加载
rmanolis4 个月前
F# secret superpower that no one has discovered for 30 years, and it will change its popularity in enterprise software.
评论 #42725111 未加载
评论 #42725513 未加载
评论 #42727423 未加载