![]() So the next, next, next level of what GHC+HLS is today. What would really be a game changer would be a compiler that could reason about time and memory complexity and give you feedback in real time about specific functions as you change them. With some positive exceptions and I count GHC+HLS among them. I don't want to sound totally dismissive, I do agree with you at some level, it is somewhat worrying where the future of software is heading when you stop to think about it. I agree that the setup you describe actually sounds cool as additional feedback to the devs but I'm not aware of existing solutions like that the setup seems complex and quantifiable benefits dubious at best. Possible is one thing, on the efficient frontier is another. Arguably these days 16/32G of RAM is neither extravagant nor crazy expensive. It's not "fair" but it is reasonable to assume that a software dev using a given tool can recognize when she needs to invest in new hardware. Also, when are you not on your own? If your system meets the recommended requirements does that really mean anything? Nope. My point was, that boundary would have to be either silly or ill defined. ![]() If project defines minimal and preferred requirements but you use the plug-in with an unsupported setup, then you are on your own, you have been warned. Software is getting too fat even when doing the same tasks :(ĮDIT2: I reported this to the project itself, see issue 716 here In that way the user will know what's happening and why.ĮDIT: I also wanted to add that some years ago it was possible to use great tools with small amounts of ram. Show a message to the user explaining that memory or cpu is not enough. Refuse to start the plug-in if minimal requirements are not provided. Show a message explaining that some features were disabled. Heavy parts could be turned off to avoid high resource consumption. Provide basic experience if machine only provides minimal ram and cpu requirements. All features should be enabled and consume reasonable amount of resources. Provide full experience if recommended requirements are provided. Plug-in should define the minimal and recommended requirements and then: I think the existence of bigger machines with more RAM and CPU cores should not be an excuse for bad user experience. Ask a question on Haskell Stack Overflow.This includes a human posting the output of a bot, such as ChatGPT.īlockchain posts must be tagged Blockchain posts are allowed as long as they are related to Haskell, but they must use the "blockchain" tag. They will be banned with extreme prejudice. Bots cannot be used to make posts or comments. Simply looking for people with interest in or experience with Haskell is not sufficient. ![]() Job postings are allowed as long as the job actually involves working with Haskell. Questions about homework are fine, but this subreddit is not here to do your homework for you. Both asking and answering homework questions is not allowed. ![]() No matter how funny, memes and image macros are not allowed. Posts about topics that are adjacent to Haskell, like for example functional programming, are typically allowed. For example a post about OCaml would only be allowed if there was a connection to Haskell. Top-level posts should be primarily about Haskell. The Haskell programming language community.ĭaily news and info about all things Haskell related: practical stuff, theory, types, libraries, jobs, patches, releases, events and conferences and more.
0 Comments
Leave a Reply. |