|
Knyteguy posted:Also has anyone tried developing with either with a Microsoft stack like MVC and SQL Server? Our entire site is a MS stack and it works great. Using MVC.NET 4.
|
#
¿
Dec 10, 2013 19:29
|
|
|
|
| # ¿ May 22, 2024 10:18 |
|
|
Thermopyle posted:I kind of wish I had a reason to use gatsby to create a site. For some reason I really like the idea of static site generators, and gatsby brings that together with my appreciation for React. I've been doing iOS app development for the past 4 years and recently I've been looking for an excuse to catch up with the horribleness that has become webdev so my skills don't stagnate too badly. This seemed pretty cool and I was able to create something pretty neat in a day.
|
|
#
¿
Aug 6, 2017 03:39
|
|
|
smackfu posted:Are there are any common languages with immutable data structures as first class citizens? Which would prevent that kind of example? Come on over to the Swift side 
|
|
#
¿
Oct 2, 2017 14:59
|
|
|
Nolgthorn posted:Server code is also in my experience not all that complex, compared to a client side app so value is reduced. Do you know how many engineers' ears just perked up and are ready to pounce on you for this statement?
|
|
#
¿
Oct 5, 2017 14:17
|
|
|
Nolgthorn posted:When I make that statement I am ignoring devops, which thanks to lots of really smart people isn't as complicated as it used to be. Load balancing and sharding and stuff like that is still pretty complicated. Yep, just keep digging that hole bud.
|
|
#
¿
Oct 5, 2017 17:11
|
|
|
prom candy posted:It's the Wild West because we also have to keep up with UI/UX trends in order to be as user friendly AND unique as possible. I loving love it though. Just keep in mind, there are plenty of other "front-end"s that need to keep up with UI/UX trends that aren't being rendered on browsers and whose tooling ecosystem isn't a complete dumpster fire! (yes, I know this thread is front end web-dev).
|
|
#
¿
Oct 6, 2017 15:09
|
|
|
I'm starting to dabble in front end web dev to keep myself up to date, and I was looking through React and saw they had some recommended starter kits: https://reactjs.org/community/starter-kits.html I played around with Next.js and two hours later I had a deployed server side rendering SPA which is pretty dope. I'm a big proponent of not using a lot of "precanned" solutions, but this one seemed nice?
|
|
#
¿
Mar 5, 2018 16:16
|
|
|
Ferdinand the Bull posted:It's good for getting MVPs up, but of course you'd want to have your entire build system understood by someone on your team if you are hinging your company's success on it not breaking in a year and no one knowing how to fix it. MVP might be pretty good. I'm thinking this could be good for a standalone microsite for us to test out some new concepts (to help break out of our monolith).
|
|
#
¿
Mar 5, 2018 23:28
|
|
|
smackfu posted:How do people handle live deployments where a feature requires compatible private API and front end changes? We have all the dev ops stuff worked out, so people stay logged in and there is no outage. But they are still running the old version of our SPA against the new backend until they refresh the page somehow. Do you version your private API just to handle that short time period? Or just try very hard not to change API? Versioned APIs are important and you shouldn't be breaking that contract with live code. If you're making breaking changes (different endpoints, properties having their names changed) and not providing backwards support, you're doing it wrong. That said, perhaps you could have a client "version" number that's passed along as a header in your API requests, and have your backend service return a specific status/response if your client's version is too old and needs to refresh. Then, in your client's networking code, have a standardize way to alert the user that they need to refresh their page (a link or something). I've never done this with a SPA before, but I imagine that could work.
|
|
#
¿
Mar 23, 2018 20:55
|
|
|
Capri Sun Tzu posted:Yeah but XML though The lesson's still the same. There are pros and cons to tightly coupling your datastore to your client-side representation.
|
|
#
¿
Apr 24, 2018 14:39
|
|
|
It's incredibly easy to do all of this with Rails or Django.
|
|
#
¿
Jun 2, 2018 04:02
|
|
|
I finally forced myself to "launch" my GatsbyJS blog: https://blog.bayphillips.com The entire thing is free as it's hosted on Github Pages, uses Contentful as the CMS and uses CircleCI to deploy updates. This poo poo is pretty cool.
|
|
#
¿
Jun 26, 2018 15:23
|
|
|
prom candy posted:Gatsby is great, I'm really looking forward to finding another project to do with it. I'm slowly trying to influence folks at work for us to start using it for marketing pages...
|
|
#
¿
Jun 27, 2018 12:19
|
|
|
Lumpy posted:So that UIkit framework you are using "just works" with React? No issues so far! It's been interesting getting UIKit + React + Gatsby specific components working as I'll have to add some of the specific classes to various wrappers (particularly the gatsby-image), but it seems to work fine. It took me a while to realize I had to pass in the UIKit specific html attributes as `data-uk-whatever` in React because it kept yelling at me. I thought the `data` part would break UIKit but it didn't.
|
|
#
¿
Jun 28, 2018 15:32
|
|
|
my bony fealty posted:That's what I've been doing at my new job, well more so taking some of our older marketing sites that were built in AngularJS and rebuilding them in Gatsby. It has been a great experience. I'm the only dev on our team though so I get to use whatever tools I want (and get solely blamed when something breaks yay). I moved over to v2 and it was fine and easy, but keep in mind it's for my stupid personal site and not used in any real production way. The upgrades to babel and webpack are cool and good, as well as making the layout a component is a smart move. I'm not sure if I'm a fan of the introduction of StaticQuery, which allows you to hit GraphQL from within components instead of having to pass things down from props. I'm still grappling with this one because I've never used a static site generator, but the notion of requesting data from within individual components sounds like a really bad code smell to me. I could foresee that being a huge issue if you start relying on it for complex systems, but alas, we're dealing with static sites. 
|
|
#
¿
Jun 29, 2018 16:52
|
|
|
Analytic Engine posted:Galaxy Brain: forcing dozens of new hires to use first guy's spaghetti architecture This is me right now...
|
|
#
¿
Jul 27, 2018 12:10
|
|
|
I *almost* have my Gatsby v2 site working with S3 and Cloudfront. Static sites are great and all, but you do have to reimplement a lot of things that traditional webservers make quite a lot easier. The last thing I need to figure out is why Cloudfront isn't gzipping my assets. Going through all of this does provide more context as to why static site services like Netlify exist and why they're worth it.
|
|
#
¿
Jul 30, 2018 15:58
|
|
|
Dominoes posted:Thanks dude. Will investigate the dets once I find a proper front-end host. I wrote up a blog post about how I got my Gatsby site hosted on S3 and Cloudfront should you choose to go down that path: https://www.bayphillips.com/blog/gatsbyjs-using-amazon-s3-and-cloudfront/. tl;dr you can use a Lambda@Edge to detect if a request is going to a "directory", and to append an index.html to the end of it. Was this more work than using something much simpler and just as (if not more) performant as S3/Cloudfront? Yes. Was it fun and gave me an excuse to tinker around in AWS? Yes.
|
|
#
¿
Aug 20, 2018 04:16
|
|
|
If you're doing .NET, why WOULDN'T you use Visual Studio? I loving miss it so much. *edit* Also, VS Code is dope and works great for so much.
|
|
#
¿
Nov 6, 2018 02:41
|
|
|
Mr Shiny Pants posted:Because you run Linux? Ionide is pretty awesome. Do people develop .NET on non Windows machines these days? I haven't done it in 6+ years so I'm definitely not up to speed on it anymore. Hadn't heard of Ionide, looks interesting 
|
|
#
¿
Nov 6, 2018 14:29
|
|
|
Ape Fist posted:Visual Studio Code is not Visual Studio and does not have the support for .NET development out of the box. You have to install a bunch of helper plugins (which bug out when it looks at cshtml files because Visual Studio Code can't figure out where Razor Syntax begins and HTML ends.) as well as a bunch of other poo poo. I think we are all on the same page with this?
|
|
#
¿
Nov 7, 2018 01:30
|
|
|
Thanks for the heads up. Looks like we're clear on that but goddamnit.
|
|
#
¿
Nov 26, 2018 19:24
|
|
|
Grump posted:Thanks. I think I'm going to end up dropping firebase and NoSQL. I know Firebase says that duplicating data is fine, but it seems like I'm basically just creating two very similar documents, at that point. Definitely for another thread, but please make sure you have a solid understanding/experience with relational databases if you're gonna start applying around (I assume from your comment on padding your resume). GraphQL is cool and new, but SQL's been around for a long time and is good.
|
|
#
¿
Jan 7, 2019 16:17
|
|
|
Munkeymon posted:Anyone know how to make Gatsby poo poo out a minimal bundle with a predictable name? Ehhh this sounds funky. As in you don't want the chunked, path based bundles? I'd steer clear of doing this, but I'd imagine you can do something to this extent by overriding/adding your own rules to the webpack config: https://www.gatsbyjs.org/docs/add-custom-webpack-config/ Doh004 fucked around with this message at 13:33 on Jan 31, 2019 |
|
#
¿
Jan 31, 2019 13:12
|
|
|
Munkeymon posted:I'm just using it as a static site generator that happens to use a framework I'm familiar with and it's slightly more annoying to clean up the old files when I copy stuff to the server. Plus I almost certainly won't need, say, the map files because I'm not doing anything complicated, so leaving them out of the build output should be fine. If you don't have a tool to handle the diffing for you (I host mine on S3 and use their CLI to sync the folder), couldn't you just clear out the folder entirely and reupload it each time. Obviously depends on the size of your site.
|
|
#
¿
Jan 31, 2019 16:29
|
|
|
Grump posted:Apparently this solution wasn't good enough because it "creates the potential for latency to cause edge cases." ... but you need the refreshed token before making the rest of the API requests...?
|
|
#
¿
Feb 19, 2019 23:38
|
|
|
bartkusa posted:Webpack renames our images with hashes of their content. This is correct and a major advantage to using modern build tooling like Webpack. It also lets you start to use aggressive cache-control headers on your static assets.
|
|
#
¿
Mar 11, 2019 19:31
|
|
|
Sistergodiva posted:We are working with a bank which has a like 3 week onboarding to get to their jira through citrix so I am assuming we can't change their server environments. It sounds like you're confusing React with something like Node & Express. Like others have said, React is not a web server that handles requests and provides responses. It's literally just HTML and Javascript that runs in the browser.
|
|
#
¿
Mar 15, 2019 04:29
|
|
|
All codebases are poo poo. Literally the moment you push code out to production it becomes tech debt. Scope, time and resources. Those are the three levers when developing software and very rarely (if ever) do we have control on all three of those things.
|
|
#
¿
May 31, 2019 15:22
|
|
|
Gatsby is dope and good with a really extensive plugin system that allows you to pull from dynamic data sources at build time to statically generate the entire site.
|
|
#
¿
Jul 8, 2019 11:24
|
|
|
Used it at last job, worked pretty well for our manual web QA work.
|
|
#
¿
Jul 22, 2019 15:24
|
|
|
As someone who was on a team building out web-apps with Silverlight back in 2010, let me just say I'm wary of web-based Microsoft UI frameworks. Blazor looks p cool though, hadn't heard of it until now.
|
|
#
¿
Aug 15, 2019 16:31
|
|
|
Careful Drums posted:imo the only thing that sunk silverlight was that it was a proprietary browser extension. Blazor is built on top of the WebAssembly standard so we can at least say it won't have that problem. Famous last words 
|
|
#
¿
Aug 15, 2019 18:34
|
|
|
And you can then ask him about it on Twitter and he'll explain it even further.
|
|
#
¿
Aug 17, 2019 13:53
|
|
|
I'd say it's also fundamentally different from how FB has handled a lot of its other open source projects before. React is good.
|
|
#
¿
Aug 19, 2019 20:00
|
|
|
Rex-Goliath posted:Oh yeah I know those exist I more want to do it as a hobby. I guess doing it on AWS would be good experience as well though. I just want to physically own the machine, I guess. I too hung on quite long about having dedicated machines because it's how I did things damnit. But then I tried out running my wife's blog on EC2 and my crappy site on S3 and Cloudfront: https://www.bayphillips.com/blog/goodbye-to-dedicated-server-hosting/ It's exactly what I need.
|
|
#
¿
Aug 28, 2019 20:55
|
|
|
Ape Fist posted:I have a young family and it's ten thousand pounds in a city where ten thousand pounds is loving huge. So I don't get to make these kinds of decisions thinking solely about myself. The usual justification to get you to move without good cause (toxic environment, dying company etc) is a 25% raise. If the 10k hits that mark, go for it.
|
|
#
¿
Sep 9, 2019 16:32
|
|
|
|
| # ¿ May 22, 2024 10:18 |
|
|
Grump posted:So I'm looking to deploy my personal site as a Gatsby site, using Nginx on Debian 9. Go use a cloud-based CI like CircleCI or Travis to do be hooked up your Github repository, build and deploy your site to your host. They're super easy and free. I use Circle to deploy my Gatsby site: https://circleci.com/gh/BayPhillips/gatsby-blog
|
|
#
¿
Oct 22, 2019 20:34
|
|