macca321

Thanks, that looks great!

I'd be really interested in the ability to put in probability ranges for cell values and run monte-carlo simulations to get the final values (Excel+montecarlo has been a pet idea of mine for years but I haven't got the time to do it)

You can definitely do this with fiddler. Very nice to use in conjunction with xip.io also

I really struggled to use it, this approach looks a bit more straightforward.

'the world' is not people already using another flavour of c#.

Why isn't .NET taking over from python/node-with-typescript projects?

If that's your intent (free, in perpetuity), why not release it under Apache or GPL or something?

Perhaps for the lower carbon output?

For some reason I really like hitting the 'submit' button via the touchscreen after filling out a web form.

I had an idea years ago using a webcam and the 'blood under fingernail' to have a trackpadless-trackpad (i.e. same as this project but on your table).

Maybe some time-rich person will fork it and do so.

Jeff's blog is really great btw., especially the Towards Moore's Law series.

https://bullet-train.io/ looks promising

You can get a pretty reasonable facsimile using some libraries I made:

Discriminated unions: https://github.com/mcintyre321/OneOf and One line value objects: https://github.com/mcintyre321/ValueOf

... and exhaustive matching: https://github.com/mcintyre321/OneOf

I'm not saying it's as good as writing F#, or that C# shouldn't include these features of course.

One line data types https://github.com/mcintyre321/ValueOf

What a grim mindset. OTOH I really underachieved at uni by not taking it seriously, and the whole system would fall apart if everyone had behaved like me.

You actually don't need to honour the links.

If a client gets a 410 when following a stored link, they can always find the new url for the resource by following links from the parent resource (this is recursive, all the way back to the root url).

Not too good for london

Yes but you still need to moderate your behaviour (and experience fear) around the police in a way not necessary in other countries.

It's a fallacy that GWT has to be at the browser automation level. And it's a lot easier to understand the point of a test if it's got GWT comments interspersed with the code.

What's tricky is when that lambda doesn't have a documented contract with the systems it talks to, doesn't have end to end integration tests, has a unique build pipeline, requires manual infrastructure creation and there are 100 others like that.

I'm not saying yours is like that, but I've definitely seen that happen.

There's a huge element when working with SPA developers of reinventing the wheels that the browser and HTTP provide.

And if that doesn't make sense, read: https://8thlight.com/blog/jason-desrosiers/2018/05/30/the-hy...

and https://8thlight.com/blog/jason-desrosiers/2018/05/30/the-hy... if you are wondering what that means

There's two kinds of REST. REST as most developers misunderstand it, and REST as Roy Fielding, inventor of REST, understands it.

For the former you can read the Microsoft REST guidelines, for the latter I suggest getting Mike Amundsen's RESTful Web APIs book.

If you do go with the latter be prepared for a lot of frustration with those who went with the former.

There are interesting parallels between problem solving textworld agents and smart hypermedia client agents.

It's also a problem for software engineers in the UK, for whom 6 months of the year utc and local time are the same, resulting in people not knowing the difference. In the rest of the world it's bleedin obvious.

A downside to inventing time I guess ;)

probably when not using a JetBrains IDE

That's EDA (Event Driven Architecture) not ES.